[pmwiki-users] Any hope for 2.2.0 stable release?

[Sameer Kumar]

Having worked with Pmwiki for only about one year, I definitely do not
consider myself an "experienced Pm'er". However, for someone like me who has
not had any programming training (I am an architect, and not the software
kind!), I have found learning about Pmwiki to be an amazing journey. This
user-list (a special mention for Hans!) and the documentation, as it exists,
have been immensely helpful and adequate for me to start from scratch and
end up with a phenomenal info-portal for my needs. I have also been
impressed by Patrick's generosity (in sharing Pmwiki with us and helping us
out whenever he could find the time) on one hand and his commitment and
focus to the principles he established on the other. I have also witnessed
the respect that Patrick commands on this user-list and have no doubt that
it is well-deserved.
Among all the opinions expressed so far on this topic, I would say that
Dave's opinion comes closest to my thoughts on this. In fact, it is upon his
instigation that I chose to chime in... Yes, Dave, I would like to
contribute "actively", to the best of my ability (in terms of both knowledge
and time). But as I said, I may have little to offer as far as code
development or developer documentation goes.

I second Mike's sentiment about the need for sensitivity on this issue given
what Patrick has been going through.

My vote is for creating a system that would support and complement Patrick
in fulfilling his vision rather than a committee that would debate the pros
and cons of his vision and in the process simply lose the sight of it!

Sameer

On Thu, Jan 15, 2009 at 6:00 PM, DaveG <pmwiki at solidgone.com> wrote:

>
>
> Henrik Bechmann wrote:
> > Step 1: declare current release out of beta
> > Step 2: identify a (for real) webmaster to take responsibility for
> > pmwiki.org
> > Step 3: create a development.pmwiki.org subsite, where we can set up a
> > wiki to begin a formal planning process (and set up a TRAC repository
> > for the current code base)
> > Step 4: fire up pmwiki-devel for *lively* discussions about related
> > issues: planning, feature discussions, organization, decision making,
> etc.
> > Step 5: follow-up from steps 1-4 <grin>...
> I agree that these steps are foundational -- although not so much on
> [2], but that depends on the definition of webmaster.
>
> Key for me is creating a structure beyond Pm (but not excluding Pm) that
> encourages and manages development within the core. I believe it's this
> level of community which is missing. This I think will encourage more
> activity in the dev and user communities. As others mentioned, developer
> documentation needs to play a role here, and with the help of some of
> the more experienced Pm'ers.
>
> And contrary to other opinions, I think Trac would be a positive start,
> communicating both what's done, but what's planned.
>
> The key issue is whether anyone beyond the voices heard so far has any
> interest in *actively* participating -- therein lies the key.
>
>  ~ ~ Dave
>
> _______________________________________________
> pmwiki-users mailing list
> pmwiki-users at pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pmichaud.com/pipermail/pmwiki-users/attachments/20090115/100ee89c/attachment.html