I'll be my curmudgeonly self:
On Mon, Nov 17, 2003 at 03:55:02PM -0500, Mike Gifford wrote:
> First PeterC, great job on cleaning up the vision for BE/PSL
> development. There are a couple of objectives for this meeting that I
> think will be useful and achievable:
>
> 1) Strengthen the Back-End developers community by providing an
> opportunity for us to discuss issues off-line.
> 2) Discussing Opportunities for common development between BE & PSL.
> Nothing needs to be set in stone, but it would be useful to brainstorm
> possibilities.
> 3) Discussing a project development roadmap. BE/PSL are pretty unique
> Open Source projects, how can we promote the development of this
> community?
There are a couple of quick answers to this that can be broached now:
- Lack of centralization/modularization in BE. There's no obvious
starting point for n00bs.
- No apparent docs. I know PeterB wrote some, but they aren't on the
BE/sf site.
- No open forum for feature requests.
I'm mentioning these here and now because they may make reasonable
starting points for our 5:30 and 6:00 discussions.
> I see the agenda looking like this (this is a draft):
>
> 4:30 - Ottawa developers arrive, drop off coats, set up laptops & eat
> some munchies.
>
> 5:00 - Developers call the 1800 number (PeterC will be called by an
> operator). Informal discussions and hello's between folk's who have
> emailed.
>
> 5:05 - Round - Introductions begin (name, location, experience with
> BE/PSL).
>
> 5:20 - Quick History of BE & PSL
> - Separate projects - both with a long history
> - OpenConcept began developing applications with PSL Code in 2001.
If possible, could we do this via email? The history, although
interesting does not require an interactive forum like a conference
call. It would also be worth mentioning on the website.
> 5:30 - Plans for the future
> - PSL plans for 0.8
^^^ looks good.
> - New BE coding/testing initiatives.
> - beautiful code
> - unitTesting
> - cvs demos
What more will be said about these initiatives than "We're doing
them"? Unless there's a desired feedback component, I think we'd be
comfortable with you saying "we've got standards, you can find 'em here,
obey 'em".
I think there's a lot of value in talking about future
design/development plans tho.
> 6:00 - Visioning opportunities for future development
> - exchangable modules
> - cross promotion
> - niche market development (NGO/Union eAdvocacy tools)
Looks good.
> 6:30 - Challenges for development & potential solutions
> - i18n
> - limited budgets
> - bringing new developers up to speed
Also might be worth adding "growing the BE devel community" -- this
will cure a few of the budget ills.
> Should we have a wiki or something to keep track of minutes, action
> items, etc?
Take minutes? Sounds like a good idea. I would volunteer, but I tend
to space out for brief periods of time during conf. calls, so I may not
be the best person. If nobody else vols, I can do it.
Thanks for putting this together Mike/Peter. It should help make
Thursday's meeting much productive.
e
-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
|
