One thought might be to have the YiPs site be thee-go-to-place for
learning about what active open source projects exist and then use the
infrastructure from things like to facilitate an SVN
repository, bandwidth for downloads, etc. Eventually we hope to be able
to utilize the YiPs AS400 for active development on open source projects
but first we have some logistical things to work through (note though that
it has a high potential of working as others in the academic community are
already accomplishing it).

To conserve on time and to get things out there quickly I think we should
start out with listing available open source options on
[1] and once
the list gets too long we can write some code to categorize all the
different entries and make them searchable. A long term goal would be to
develop patterns for developing and delivering the open source
tools/products (i.e. all open source projects follow a similar/same
pattern for installation/uninstall/updates/etc).

That's my $.02

Aaron Bartell
From: [3]BMay@xxxxxxxxx Date: 07/07/2009 09:05 AM


I'm playing catch up on the posts, but I can definitely create a place on
the YiPs site to host open source projects. I can set up something as
simple as a section in our WIKI in a matter of minutes. If we want
something more robust, I'm sure I can find the right tool and get it
ported quickly. Maybe a FusionForge (which is a fork from the original
SourceForge code base) port would do the trick. So I guess the question
is quick and dirty or full featured. I'm leaning more toward doing it
right the first time.

Brian May
Project Lead
Management Information Systems
Garan, Incorporated
Starkville, Mississippi

Young i Professionals


Visible links
3. mailto:BMay@xxxxxxxxx

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].