## Announcement - OSSEC Moving to Github
OSSEC is moving from bitbucket to github, and in the process moving to a
new method for accepting contributions. This is an exciting change
that we feel will help push OSSEC forward in 2014 and further into the
future.
* oRFC:1 Collective Code Construction Contract [1]
- (Adapted from ZeroMQ's C4 [2]).
[1]: https://github.com/ossec/ossec-docs/blob/master/docs/oRFC/orfc-1.rst
[2]: http://rfc.zeromq.org/spec:22
The overall goals of the change are to allow OSSEC to be more
dynamic, agile, and quicker to respond to the needs of the community.
This change will not be without issues or problems, but we aim to make
it as seamless as possible. To do this we are committing to the
following task to be completed 7 days from now:
1. Port all code to github
2. Port all Open Issues to github issues
3. Port all Open Pull Requests to github Pull Requests
## 1) Porting code #################################################
This is currently done every 30 minutes (when hg-git does not break).
We have set up and enabled [githib.com/ossec/ossec-hids][3]
This will continue till to the cut over date of Feb 7th 2014.
## 2) Port Open Issues #############################################
We will copy all open issues from Bitbucket to github. Due to the api
available, the reporting user and all comments on issues will show up
as the user performing the migration. Test runs are being preformed
to github.com/jrossi/issue-migration-test[4]
## 3) Port Open Pull Requests ######################################
This process will be the hardest, and will be the hardest to detail,
but we shall attempt it here.
Contact pull request author to request they move to github and resubmit
using github. If no response is received preform the following:
1. Create github.com/ossec/bitbucket-pull-requests as a fork of
github.com/ossec/ossec-hids/
2. Export each Pull Request as a patch bb-gh-pull-request-##.patch
3. Import each patch into a branch named bb-gh-pull-request-##
- Apply correct author/email git information so no information
is lost.
4. Create a github pull request for each branch.
For authors who email addresses match between githib and bitbucket
everything will show up as expected. Authors can also use github
email settings[5] to add second or third email address.
Once completed, each pull request will stand on its own and be reviewed
for merging based on the Collective Code Construction Contract.
[3]: https://github.com/ossec/ossec-hids
[4]: https://github.com/jrossi/issue-migration-test/issues
[5]: https://github.com/settings/emails
--
---
You received this message because you are subscribed to the Google Groups "ossec-list" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
