Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Adding project explanation #16
Hi thegreystone, welcome to this OpenJDK project and thanks for contributing!
We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing
If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing
Mailing list message from Mario Torre firstname.lastname@example.org
Awesome, so now not only we need to track github as a whole, but also
I still think that the old good mailing list are the way to go ;)
Mailing list message from Erik Helin email@example.com
On 7/1/19 3:59 PM, Mario Torre wrote:
I was just about to ask Marcus to update the description for the patch,
I think it is fairly obvious that we are still tuning a few knobs and
I want to highlight that this not a normal situation, label updates on
We also like mailing lists! I use skara-dev all the time to keep track
The above doesn't mean we don't have a few bugs, Robin is currently
Mailing list message from Marcus Hirt firstname.lastname@example.org
Haha. I mostly wanted to take it for a spin. Seems some good came out of it too. ;) I've updated the GitHub issue with a link to the discussion on Twitter.
On 7/1/19 3:59 PM, Mario Torre wrote:
I was just about to ask Marcus to update the description for the patch, as I don't follow nor use Twitter myself.
I think it is fairly obvious that we are still tuning a few knobs and that Skara is under active development, making steady progress day by day. We did run into a (pretty hilarious) Skara bug for this PR from Marcus, to which I reacted with a comment containing a few emojis. The comment was made in response to a number of label updates by the bots, which is why the comment is out of context here on the mailing list.
I want to highlight that this not a normal situation, label updates on pull requests do not in general convey enough useful information to merit relaying them to a mailing list (nor comment on them). We primarily use labels to aid people who want to sort pull requests in various ways. We could send label updates to the mailing list as well, but I think it would just annoy people (it would annoy me at least).
We also like mailing lists! I use skara-dev all the time to keep track of patches, comments and discussion. I want to be very clear that the goal is not to replace the mailing lists, we continue to work very hard to ensure that a contributor who wishes to use the mailing lists and the CLI should have a great experience.
The above doesn't mean we don't have a few bugs, Robin is currently working on making the mailing list experience better. If you have any additional feedback after following skara-dev then we'd be happy to hear it! And as usual, if you see something you think is a bug, then please file one 0.
@thegreystone This change can now be integrated. The commit message will be:
Since the source branch of this PR was last updated there have been 58 commits pushed to the
Since there are no conflicts, your changes will automatically be rebased on top of the above commits when integrating. If you prefer to do this manually, please merge
As you do not have Committer status in this project, an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@edvbld) but any other Committer may sponsor as well.
Your commit was automatically rebased without conflicts.