Team JA2 Stracciatella

[JAsmine-ja2 NA]

Let's get together in a mail chat and see what will happen :)

ja2stracciatella at gmail dot com

This is supposed to be some kind of basis so that we can discuss the status/future of this project.

[Jaka Kranjc]

I've messaged gennady through bitbucket. I'm reachable through jaka+bitbucket at ocistimo.si .

I think we have to do at least these things:

• count ourselves
• see who's up to what
• see who's up for what
• create the bitbucket team / give access
• (harder) decide how much chocolate we want and how
• report to BP

[JAsmine-ja2 NA]

I've massaged gennady through bitbucket before. Last time he was here seems to be about two months ago. Since he mentioned to me that he thinks about abandoning the project, I guess that he might have done so... He was working on this solo for quite some time with ~zero help or feedback.

Your list of things to do is a very good start. I think, the mail-chat (ja2stracciatella at gmail dot com) would be a good way to count ourselves.

[Jaka Kranjc]

Well we do have his email, so that's not a problem. What I'd like to avoid is the need to create another fork, since then bug information is lost (or numbering broken) and a bunch of stuff would have to be manually copied over. Plus the obvious inconvenience of a new address, remote.

[Jaka Kranjc]

Ehhh, silly bitbucket — it appears a fork will be unavoidable. :( I made a test repo and team and it turns out you can only create new repos for the team or import old ones (but not just changing ownership). HMPF

[Stefan Lau]

What about moving to Github then? Imho it provides a way better developer experience and some of the other features could be useful to us (e.g. Github pages for a more user-friendly project presentation).

Edit: There is even a migration tool that should keep links between issues/users (did not test it though): https://github.com/jeffwidman/bitbucket-issue-migration

[Jaka Kranjc]

Heh, with that, it does gain an upper edge. I'm all for github, though I'd also like to hear from more people.

[JAsmine-ja2 NA]

I think anything that will push allow development of this project to continue is a good thing. So, I approve moving to Github.

[Gennady Trafimenkov]

Hello, guys!

I am glad to see you all.

It is probably a good idea to create a team on BitBucket or GitHub to continue development and support of the project.

Unfortunately I don't have any more time to spend on this project. So, I can't be the maintainer of the project (administer push access, merge pull requests, test and release new versions).

How about this plan:

• you organize a team on GitHub or BitBucket and continue further development
• I will make a notice on this repo that all the development have moved to new repo and make a link to it
• I will help with the development in the new repo if I have more time in the future

What do you think?

[Stefan Lau]

+1 on that.

I created a team on github and invited @gennady. If you send me your github usernames I can add you all as well, then we can continue from there and setup the development process.

[JAsmine-ja2 NA]

+10k on that :D

[Jaka Kranjc]

Cool, thanks for chiming in! My gh username is lynxlynxlynx.

Once we have a repo set up, I'll write the usual tips for git remote changing (no need to redownload).

edit: it's as simple as running

git remote set-url origin https://github.com/ja2-stracciatella/ja2-stracciatella

[Jaka Kranjc]

See edit above. I tried the migrator script and a dry run worked fine, so I'll just do it for real now.

'tis done: https://github.com/ja2-stracciatella/ja2-stracciatella/issues

the copy of this bug now contains a more detailed todo. Time to notify more of the bitbucket committers.

[Gennady Trafimenkov]

I've switched the landing page to Wiki and made the announcement about the move to GitHub. Check this out https://bitbucket.org/gennady/ja2-stracciatella

I guess we can resolve this issue and move to GitHub completely.