We're moving!

[jeff-h]

Thanks to the efforts and input from an outstanding bunch of people, MacGap has grown to the point where we can benefit from better and bigger infrastructure. So we've become a GitHub organisation.

Over the coming week or so we'll be migrating over to https://github.com/macgapproject where we will have multiple repositories for all the different things we're working on: MacGap 1.x, MacGap 2.x, a MacGap website and so forth.

Any thoughts / questions very welcome.

[perfaram]

Guess I can delete the beta organization (@macgap-dev) ?

[perfaram]

And, will this repo's ownership be transfered to @MacGapProject, or just forked ?
IMHO, it would be better to transfer.

PS : I apply to become a member of @MacGapProject - if possible, of course.

[jeff-h]

@perfaram Yes, please delete the -dev. Thanks again for your input and initiative on this. It would be great to have you as a member in the new structure. I'm keen to keep just one person responsible for each repo in most cases, at least to start with, so the following ideas are looking for a lead:

• a "getting started" app, which is a downloadable-from-the-website pre-compiled MacGap app which serves as a very quick entry point into using MacGap — no Xcode even required, just supply HTML, CSS & JS.
• a sample app, illustrating the use of some of the MacGap API in a real-world situation; ideally this will be submitted to the Mac App Store as well.
• your ideas here :)

[gobijan]

nice!

[rawcreative]

Just as an FYI, because of some of the new features I've put in/am putting into MacGap 2, especially the ones that require entitlements/special access for sandboxing, users who want to pick/choose those features (or eliminate them) will need to use Xcode at some point (or at least have it installed). I'm creating multiple build targets that toggles these features on/off so they won't even be compiled in the shipped app. I'd actually like to replace the current ruby gem with a shell script that handles everything without going into Xcode but even so, xcode will have to be installed for it to work.

[jeff-h]

I'm creating multiple build targets that toggles these features on/off so they won't even be compiled in the shipped app.

This sounds really great!

In relation to the "getting started" app idea mentioned above, this should be fine as we'd probably make the entire API available in that (unless there's a danger in that?).

[jeff-h]

I'd actually like to replace the current ruby gem with a shell script

You know what could be cool... if we replaced it with a MG2 app :D

[perfaram]

Little incursion to tell everybody that the beta organization (MacGap-Dev) has been deleted !