I agree about having special place for projects with "work in progress"
status. I usually prefer to do such things as separate branches in Git &
use Github to publish them. I really don't know how it's better to organize
this for bzr (and I don't want to spend much time to learn it - I would
hack CEDET instead)...
On Wed, Mar 6, 2013 at 2:47 AM, Eric M. Ludlam <eric@...:
> On 03/05/2013 04:21 PM, David Engster wrote:
> > Eric M. Ludlam writes:
> >>> - linemark.el
> >> Hmmm. It is used by the matlab-emacs project on sourceforge. And
> >> someone copied that to support B++, or some language like that.
> > Maybe we could check it in there, then. I'll look into it.
> >>> - ast.el: This was used by David Ponce for the Wisent C-grammar,
> >>> is already in obsolete. I'd absolute love to see someone picking
> >>> this up, but there's still a *lot* of work to be done to reach
> >>> same feature-set as our current Bovine grammar (like, extending
> >>> for C++...).
> >> There should be an unfinished projects area, like contrib. There are
> >> lots of good ideas around that never quite make it, and just need
> >> someone with the drive to make them work. I think the maven support was
> >> like that for a while.
> > I'm not happy with the 'contrib' directory at all. Most of the stuff
> > there isn't working, and we regularly get bug reports about it. I also
> > wouldn't encourage anyone to really work on that stuff, since we don't
> > have papers for it. It's really unfortunate. I'd actually like to
> > discourage people to use packages from there.
> Hmmm. I can see your point, as that stuff did not convert well. In the
> old system they didn't really take up much time. They are kind of
> home-less now though.
> > Anyway, regarding and 'unfinished' directory for stuff like the Wisent C
> > grammar, I'm all for it. What else should go in there?
> To be a bit roughshod about it, anything not adopted into Emacs proper.
> It could include Alex Ott's new java EDE packages, Arduino/Android
> support, cogre, and anything else not adopted.
> That would make it pretty clear what was going on during merges.
> To be more conservative though, projects like Alex's java support could
> just start there, and move into the main directories when "done". Alex
> would have to let us know if those packages are "ready" for the mainline
> at the moment. I don't really know since I don't code much Java.
> I can't think of anything else off the top though.
> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
> endpoint security space. For insight on selecting the right partner to
> tackle endpoint security challenges, access the full report.
> Cedet-devel mailing list
With best wishes, Alex Ott
Twitter: alexott_en (English), alexott (Russian)