contrib repository

[Brandon Rohrer]

BECCA developers (especially Matt),

There are a couple of pieces of BECCA-related code, such as the server.py module a new world I'm working on, and hopefully a q-learning.py module, that aren't necessary for the function of the BECCA core, but are interesting, useful, and should be widely available. I understand that some projects, Drupal in particular, have separate 'core' and 'contrib' repositories, where 'core' is essential, lean, and highly reviewed, and 'contrib' is more 'anything goes'. I like that model, and think it might be time to set up something similar for BECCA. I'm hopeful that having a 'contrib' repository will make it just that much easier for a developer to share their code. Any comments or suggestions on the best way to go about this?

Brandon

[Matt Chapman]

Hi Brandon,

OpenBECCA.org was set up specifically to support this. :-)

Log-in and visit:

http://openbecca.org/node/add/project-project

...and let me know where you get stuck, as there are at least a few steps I need to do to publish the directory of contrib projects, which will appear on the "Extend" page once we have something to show there.

Someone should nag me to update my LEGO Mindstorm Agent for the python version and publish it...

--
All the Best,

Matt Chapman
Ninjitsu Web Development
http://www.NinjitsuWeb.com
ph: 818-660-6465 (818-660-NINJA)
fx: 888-702-3095

http://www.linkedin.com/profile/view?id=13333058

If you want to endorse my skills on Linked In, the most valuable endorsements to me are "Open Source" and "Software Development."

--
The contents of this message should be assumed to be Confidential, and may not be disclosed without permission of the sender.

[Brandon Rohrer]

Matt, you are a step ahead of me. That's very cool. 

When I jump to that page I get a "Coming soon" notice, and when I try to create a project I get a "Hmm, you're not supposed to do that" notice. Maybe I need to be added to an access list?

Brandon

[Matt Chapman]

I fixed up permissions; now anyone can create Projects.

[Brandon Rohrer]

Thanks! I can get in now.

Can you help me understand--what's the relationship between an openbecca.org project and a github project? Is the one an interface to the other? Or are they independent things?

[Matt Chapman]

At the moment, they are two entirely different things; the field for storing the github URL is a convenience only.

Openbecca.org will only host packages; developers will want to host their VCS elsewhere, github being the recommended option.

For now, a project maintainer must manually create a package/zip/tarball for their project, or download it form github, and then manually upload it as a release for their project. In the future, I hope to be able to automatically generate packages from github from branches and tags, but I haven't got around to implementing that yet.

[Brandon Rohrer]

OK, just checking. I saw the nice 'core 0.4.x release' announcements on openbecca.org and wondered if those were automatic or you created them manually. Now I know :)