Neo is back at SourceForge (partly)

[Erik Doernenburg]

Ok, it was slightly more complicated than I expected but the most
important parts of Neo are now back at SourceForge.

If have exported the entire source history from the Codehaus CVS
repository and imported it into the SVN repo for the Neo project at
SourceForge. (It's currently importing but should be finished in a few
hours.) I'm quite sure all the mime types and line endings are set
correctly, and I even fixed a few errors from the CVS repo at the
Codehaus but it would be great to get confirmation that the version on
SourceForge definitely works.

Michael (aka pcbender) is now a committer on the neo project at
SourceForge so development can continue without forking Neo. That
said, we have decided the best way forward would be to have the old
source under neo1/trunk and the new .NET 2 line under neo2/trunk. I'll
put the tutorial and websites under their own top-level dirs in a few
days, and I hope Michael can import his version from google soon, too.

I have also moved the website back to neo.sourceforge.net but there
are a few items left to fix up. I'll do this in the next few days and
then I'll put a redirect from neo.codehaus.org to neo.sourceforge.net.


What we need to decide now is the following:

* Do we want to keep the mailing lists at the Codehaus or do we want
to move this to  SourceForge, too? Actually, there are mailing lists
for neo at SourceForge already.

* If we want the mailing lists off of Codehaus, I would suggest to use
the forums on SourceForge for all user related bits, mailing lists
feel quite dated and the barrier to asking questions (from an end user
perspective) is higher if they have to subscribe to a mailing list
first. I think we should still have a mailing list for 'dev' stuff,
i.e. further development of Neo itself.

* Do we want to keep using the Jira bug tracker at Codehaus or do we
want to move to the SourceForge one? This isnt a no-brainer because in
my opinion the bug tracker at SourceForge sucks and Jira is quite
good.

* Then there is all the content on the Neo wiki at Codehaus.
SourceForge now offers a Wiki but I don't see how we can move the
content accross automatically. Any ideas?


Other tasks left are:

* Change CruiseControl Live to monitor SVN at SourceForge. I'm on that.

* Tag the 1.4.2 version (which we forgot on Codehaus). I'll do that
but have to wait until the import is complete.

* Make past releases of Neo available on SourceForge. I'm quite
tempted to just put 1.4.2 there but if anyone has a good reason....


erik

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

[Erik Doernenburg]

On 01/10/2007, Erik Doernenburg <erik@...> wrote:
> I have also moved the website back to neo.sourceforge.net but there
> are a few items left to fix up.

I've mostly finished this, if anyone can have a look at
http://neo.sourceforge.net to confirm... The 'support' page still
needs updating but we first need to decide which mailing lists /
forums we want to use.


> * Tag the 1.4.2 version (which we forgot on Codehaus). I'll do that
> but have to wait until the import is complete.

Done.


> * Make past releases of Neo available on SourceForge. I'm quite
> tempted to just put 1.4.2 there but if anyone has a good reason....

Done.


erik

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

[Artem-5]

Hi Erik,

Thursday, October 4, 2007, 4:08:06 AM, you wrote:

> On 01/10/2007, Erik Doernenburg <erik@...> wrote:
>> I have also moved the website back to neo.sourceforge.net but there
>> are a few items left to fix up.

> I've mostly finished this, if anyone can have a look at
> http://neo.sourceforge.net to confirm... The 'support' page still
> needs updating but we first need to decide which mailing lists /
> forums we want to use.

Just two minor things. We could encourage the users to use the forums
instead of the user mailing list (at the home page)? And we could
somehow forward the visitors of the sf project page to the codehaus
jira. Right now they have to go to the project website, find the
Support link, and finally go to the tracker. This kind of discourages
from adding new issues.

Artem


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email