Requirements for hosted projects

So you have something for eCos which you'd like to have hosted at eCosForge.net ? Here's what you need to do:

subscribe to the ecosforge-discuss mailinglist, in case you're not yet subscribed
send an email to the ecosforge-discuss mailinglist where you introduce your project/software
wait for a Go from the maintainers of eCosForge
get an account
add your project to svn

When introducing your software on the mailing list, please explain

The purpose

What kind of software is it and what is it supposed to do ? Both original software and ports of existing software are accepted.

eCos compatibility

Which version of eCos is required for your project ? Your project should work with current eCos cvs, or at least with eCos 2.0.

The licensing

The goal of eCosForge is to foster the development of free software for eCos, so that eCos continues to grow. eCosForge provides a free service (as in beer), so naturally only free licenses (as in speech) are accepted. This means any of the GPL-compatible free software licenses listed on the GNU license list page is accepted.
In order to minimize license issues, if you are the original author of the software and have the choice we recommend to use the 3-clause BSD license or the eCos 2.0 license. This way there won't be any licensing problems.

The maturity

How mature is the code ?

pre-alpha: You have some code, but it's still in its beginnings and except for people developing the code there is nothing really usable yet.
alpha: There is code which basically already does what it is supposed to do. It has bugs and doesn't have all planned features yet.
beta: The software is basically working. It has more or less all planned features and is usable with some glitches here and there. So basically it still needs some stabilizing.
stable: It's working code, and there are no serious bugs when used for the intended purpose.

The state of development

in development: You are actively working on the code.
maintainance: The code is stable and feature complete (for you), so there's no need to work a lot on it but you maintain it.
up for adoption: For whatever reasons you can't work on the code anymore but you want to preserve it for others.

All three states are ok. If your software is stable and mature please also state why you want it hosted on eCosForge.net instead of the main eCos cvs. Once you got the Go, add it to the eCosForge subversion repository. The repository has the same structure as the eCos cvs. You will also need to have a ChangeLog ? file as every package in eCos has and add a wiki page for your project. This page must contain the four points listed above: Purpose, License, Maturity and State. This is to help the user about the applicability of the software for his purposes.

Copyright assignment state

If you plan to commit your work to main eCos cvs once work is done here on eCosForge, you will need a copyright assignment then. It will help the process of getting your software into eCos cvs if you state here what the current state of copyright assignments is.
For using eCosForge no copyright assignment is required, this is only if you plan to commit it to the main eCos cvs.