Hi guys,

Quite simply, the reason for this development is this: If you're going
to do something, do it right. If we're going to host projects on
OSFlash, it needs automatic signup and it needs an online
administrator so that project leaders can add users, etc. That's the
way to do it right. Either that, or we don't host projects and mailing
lists. The current system of manual signups just isn't working and
it's not fair to people who want to host projects on OSFlash.

In short, either:

(a) All project migrate to Google Code (including mailing lists) and
OSFlash remains as just the wiki and the OSFlash mailing list or

(b) We keep hosting projects but we do it right.

Personally, I vote for (b) but I'm interested in hearing how you feel
about this too.

Aral

On 5/4/07, Scott Hyndman <[EMAIL PROTECTED]> wrote:
> Oh, you know that. I have _got_ to stop answering before reading
> entire emails. ;)
>
> Scott
>
> On 04/05/07, Scott Hyndman <[EMAIL PROTECTED]> wrote:
> > Google will give you more space if you ask you know.
> >
> > Scott
> >
> > On 04/05/07, John Grden <[EMAIL PROTECTED]> wrote:
> > > I'm not sure hosting at OSFlash.org is really a big issue IMHO.  I mean,
> > > I've already pointed plenty of people to google code and I myself have
> > > opened up repositories there for my own projects (pv3d is currently out
> > > there).  It's nice for the project leads so they can manage their users, 
> > > see
> > > download stats, manage downloads, source etc, - it's pretty nice.  The 
> > > only
> > > downside is the amount of disc space you get up front (100mb).  For Red5, 
> > > we
> > > couldn't possibly move out there.
> > >
> > > As for mailing lists, I think it's good to have that hosted on OSFlash - 
> > > it
> > > definitely is something that consistent and any time someone's asked for a
> > > change in mail settings, it's something I do right away because it's so
> > > easy.  And most of the time, I don't have to touch a thing, the lead has 
> > > all
> > > the power to modify the account.
> > >
> > > So the issue as I know it is, google only has so much room, but you can
> > > request more.  But there's not guarantee.  I would agree though, we do 
> > > need
> > > work on presentation on the site and I'm sure we could brainstorm some 
> > > great
> > > ideas for tools to add to OSFlash.org for the developers to present their
> > > projects.
> > >
> > >
> > > On 5/4/07, Scott Hyndman <[EMAIL PROTECTED]> wrote:
> > > > I was thinking the same thing, but I didn't want to say anything and
> > > > appear callous (not to say you were Nicolas). Maybe someone could
> > > > explain why they feel being hosted by OSFlash is important?
> > > >
> > > > Scott
> > > >
> > > > On 04/05/07, Nicolas Cannasse <[EMAIL PROTECTED]> wrote:
> > > > > > Hi guys,
> > > > > >
> > > > > > A quick email to give you a heads up on what's happening with the
> > > > > > OSFlash web site:
> > > > > [...]
> > > > > > We're just starting out on this and it will take approximately a 
> > > > > > month
> > > > > > of time for us to get the new system in place.
> > > > > >
> > > > > > Here's to a new and improved OSFlash in the very near future! :)
> > > > >
> > > > > Hi,
> > > > >
> > > > > This is great news to see that some work is being done on OSFlash.org,
> > > > > and I surely don't want to discourage it but I think it could be 
> > > > > better
> > > > > used for other stuff.
> > > > >
> > > > > In particular, creating and maintaining an automatic system for source
> > > > > code repository and mailing list is quite time and resources 
> > > > > consuming.
> > > > > Especialy since there's already some very good alternatives such as
> > > > > Google Code (http://code.google.com) and Google Groups
> > > > > ( http://groups.google.com) or other equivalent services that are easy
> > > > > and free to use, with an high level of reliability and support.
> > > > >
> > > > > Instead, I would like to see more work being done on structuring the
> > > > > OSFlash.org website, presenting each project and writing documentation
> > > > > that tells people how/when to use a particular library or tool. I 
> > > > > guess
> > > > > this would be a lot more efficient than reinventing the wheel.
> > > > >
> > > > > Again, work being done OSFlash is always good news,
> > > > >
> > > > > Best,
> > > > > Nicolas

_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org

Reply via email to