For the past 4 years or so I have provided quite a few AS3 APIs as Open Source to the Flex Community, via my blog. These APIs can typically be found at the Open Source AS3 APIs page however, the page is basically just a URI to a series of arbitrarily added AS3 source classes. It was originally intended to simply serve as a convenient location to access the source, and it had always been my intention to eventually break out all of these APIs into seperate SVN projects.
So with that being said I am finally in the process of making the structural changes I had originally envisioned. Moving forward I will begin the process of creating seperate SVN projects for these Open Source APIs; with the primary goal being to provide practical APIs that only require minimal (if any) dependencies on additional libraries, complete test coverage via Flex Unit 4 and Mavenized builds.
The first project to move over to the new project structure will be the AS3 collections project as the classes in this package, specifically HashMap, have proven to provide the most value according to community feedback.
So stayed tuned!
Awesome news, but is there a particular reason you have chosen SVN over Git?
I understand that most Flash developers are currently more comfortable with SVN than Git, but I don’t believe that’s a strong enough argument. Hosting the code over at GitHub (for example) would allow anyone to contribute in a truly Open Source fashion. SVN just feels very anti-OS and static to me these days: commit permission is required from the admin which significantly raises the barrier-to-entry (esp for quick, once-off contributions).
Regardless, I dig your code, am happy that you share it, and look forward to seeing it move forward.
Mavenized builds, nice…
If you need any help setting it up or even on publishing artifacts at central, lemme know, I probably can help.
VELO
Good news !
What licence will you choose ? No GPL No GPL No GPL 😉
The Licensing will most likely remain the same: MIT X11 License, which is GPL-compatible. However, I may consider other alternatives.
Awesome news. Thanks a lot!
hello eric, did you public the code or the project has been stopped? Thanks.
Hi Jadd, I actually just setup the repository in SVN and am now in the process of setting up a public maven repository for artifacts. Should have something published this week.
Hey Shaun, while I prefer SVN I wouldn’t necessarily say that I am biased. Essentially, it comes down to accessibility and the most widely adopted and prevalent source control solution at this time is SVN. So my decision is really based on this.