Re: [Back-end-development] Re: Re: Fwd: Re: backend -> phpslash questions

On Tue, Nov 18, 2003 at 11:59:48AM -0500, Mike Gifford wrote:
> 
> > On Mon, Nov 17, 2003 at 03:55:02PM -0500, Mike Gifford wrote:
> ...
> > > 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. 
> 
> Is this including or excluding the work done by the PSL folks on M8?

  I don't know anything about M8. All I know is that I still don't know
where to start writing a new module, even after I've read the BE docs
and the PSL docs. 

> >   - No apparent docs. I know PeterB wrote some, but they aren't on the
> >     BE/sf site. 
> 
> The BE docs have been posted to the list multiple times.  When you
> install BE, you see them on the default screen when you log in:
> 
> Help Screens 
> ?Developer's Guide
> ?Help with text formatting

  Yep, got 'em. I'm going to post the feature list from here onto the BE
site. I've checked the architecture section, but there isn't much about
API/module-layout there. Is there another section I should look at?

  Additionally: There seems to be some sort of tree structure in BE's db
implementation. I didn't see much about it (notably how to extend it). 

...
> >   - No open forum for feature requests. 
> 
> What's wrong with:
> http://sourceforge.net/tracker/?group_id=6763&atid=356763

  Good point. I stand corrected. 

[re: agenda]
> > > 5:30 - Plans for the future 
> > > 	- PSL plans for 0.8
> >   ^^^ looks good. 
> 
> The PSL Plans?

   Yah. I look forward to hearing about them. 

> > > 	- 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". 
> 
> The more stuff that we can do over the net the better, but I think it is
> useful to what has happened in the last month or so to ensure that the
> code is as robust as possible and as attractive to new developers as
> possible.

  Okey doke. 

> >   I think there's a lot of value in talking about future
> > design/development plans tho. 
> 
> I've posted the agenda here and moved things around a little:
> http://www.openconcept.ca/be_wiki/index.php/DevelopmentMeetingAgenda
> 
> How much time do you think this should take and what type of a
> structure/talking points would you see in it.  Ideally we're moving to a
> roadmap for future releases, so what do we need.

  A list of features cross ref'd to release dates. I'm not too sure
which features are on the horizon, but it would be good to articulate
those. 

  Personally, I'd love to see us move to a sleek, clean module system
(like Drupal's) that makes it super easy to write, (un)install, and
configure modules. I'm not willing to devote a serious amount of time to
this until I get paid to do it though. =P

e


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/