I have no objections here and think we should go for it for the confluent
project.
We should be able to ask contributors fork the project and submit pull
request for merge back to master.
Do we need to submit the patch to the mailing list? I'm thinking we
should slowly decrease the dependency of the xcat-user mailing list for
projects natively hosted in GitHub.
We can subscribe/follow the confluent project and would get notifications
in our email anyway when there is activity...
- Victor
From: Jarrod Johnson <[email protected]>
To: "xCAT Users Mailing list ([email protected])"
<[email protected]>
Date: 07/14/2015 05:10 PM
Subject: [xcat-user] Switch confluent over to github primary for
source access
Does anyone have any objections to switching over at least the confluent
repository to github as the primary git origin?
I'm also suggesting that the flow for contributors that are not
maintainers can either be:
-patch submitted to mailing list
-pull request on github
-Some other publicly accessible git origin
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
