Hello,
I setup the mirror of Kamailio github repository to kamailio.org, can be seen online at: - http://git.kamailio.org/gitlist/index.php/kamailio/
Mirroring is triggered by a push to github, so it is pretty much in real time.
Right now the commit and mirroring flow is:
- commit to git.sip-router.org triggers mirroring (push) to github, which triggers a mirroring (fetch) on git.kamailio.org
Practically with a commit pushed directly to github, the first part of the above is skipped.
All seems to be ok, my last commits were done to test the mirroring including the notification emails - I will send a separate message about what we can get there.
The missing parts are the deployment of gitweb in order to have the links from archived email notifications still valid and pointing git.sip-router.org to kamailio mirror server.
Considering all above, I propose to stop committing to git.sip-router.org and pushing to github starting either next Monday (Dec 15) (or Wednesday (Dec 17) if not ready by Monday). Existing developers have to send me the github username to add it to kamailio project.
Any suggestions and comments are welcome!
Cheers, Daniel
Hello Daniel,
In case of moving users to githup, what should be with current users? As I understand, should be githup'ed users?
Thanks!
2014-12-08 11:44 GMT+03:00 Daniel-Constantin Mierla miconda@gmail.com:
Hello,
I setup the mirror of Kamailio github repository to kamailio.org, can be seen online at:
Mirroring is triggered by a push to github, so it is pretty much in real time.
Right now the commit and mirroring flow is:
- commit to git.sip-router.org triggers mirroring (push) to github,
which triggers a mirroring (fetch) on git.kamailio.org
Practically with a commit pushed directly to github, the first part of the above is skipped.
All seems to be ok, my last commits were done to test the mirroring including the notification emails - I will send a separate message about what we can get there.
The missing parts are the deployment of gitweb in order to have the links from archived email notifications still valid and pointing git.sip-router.org to kamailio mirror server.
Considering all above, I propose to stop committing to git.sip-router.org and pushing to github starting either next Monday (Dec 15) (or Wednesday (Dec 17) if not ready by Monday). Existing developers have to send me the github username to add it to kamailio project.
Any suggestions and comments are welcome!
Cheers, Daniel
-- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hello,
you have to make a github account for yourself and give me the user id you've chosen. You will be able to push commits directly to github kamailio repository.
If you have missed the initial message on this topic (sent more than one month ago), practically we have to decommission an old server that is hosting now the git repository and we were looking to lift the overhead of user management and operating system maintenance, along with incurred costs.
If it was a concern for someone, git commits are associated to the email address, therefore the old ones are still associated with you (as a matter of fact, right now we have a real time clone to git hub).
Cheers, Daniel
On 08/12/14 15:59, Konstantin M. wrote:
Hello Daniel,
In case of moving users to githup, what should be with current users? As I understand, should be githup'ed users?
Thanks!
2014-12-08 11:44 GMT+03:00 Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com>:
Hello, I setup the mirror of Kamailio github repository to kamailio.org <http://kamailio.org>, can be seen online at: - http://git.kamailio.org/gitlist/index.php/kamailio/ Mirroring is triggered by a push to github, so it is pretty much in real time. Right now the commit and mirroring flow is: - commit to git.sip-router.org <http://git.sip-router.org> triggers mirroring (push) to github, which triggers a mirroring (fetch) on git.kamailio.org <http://git.kamailio.org> Practically with a commit pushed directly to github, the first part of the above is skipped. All seems to be ok, my last commits were done to test the mirroring including the notification emails - I will send a separate message about what we can get there. The missing parts are the deployment of gitweb in order to have the links from archived email notifications still valid and pointing git.sip-router.org <http://git.sip-router.org> to kamailio mirror server. Considering all above, I propose to stop committing to git.sip-router.org <http://git.sip-router.org> and pushing to github starting either next Monday (Dec 15) (or Wednesday (Dec 17) if not ready by Monday). Existing developers have to send me the github username to add it to kamailio project. Any suggestions and comments are welcome! Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> - http://www.linkedin.com/in/miconda _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On 12/08/2014 09:44 AM, Daniel-Constantin Mierla wrote:
Considering all above, I propose to stop committing to git.sip-router.org and pushing to github starting either next Monday (Dec 15) (or Wednesday (Dec 17) if not ready by Monday). Existing developers have to send me the github username to add it to kamailio project.
Are we going to use the github issues instead of our flyspray? Do we need to migrate open issues to github then?
Cheers, Victor
I am for using github -- besides it will integrate better with git repository, flyspray is slow developing (if still does it).
We need to review and see what items there need to be migrated ...
Can be done later, but if anyone wants to start, he/she is welcome.
Cheers, Daniel
On 09/12/14 21:01, Victor Seva wrote:
On 12/08/2014 09:44 AM, Daniel-Constantin Mierla wrote:
Considering all above, I propose to stop committing to git.sip-router.org and pushing to github starting either next Monday (Dec 15) (or Wednesday (Dec 17) if not ready by Monday). Existing developers have to send me the github username to add it to kamailio project.
Are we going to use the github issues instead of our flyspray? Do we need to migrate open issues to github then?
Cheers, Victor
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
If we are commiting to github, then we should use the github tracker because it offers a tight integration. If possible, we should move existing issues from flyspray to github or just leave them there until closed, but new issues should be tracked in the github tracker.
Regards, Ovidiu Sas
On Tue, Dec 9, 2014 at 4:57 PM, Daniel-Constantin Mierla miconda@gmail.com wrote:
I am for using github -- besides it will integrate better with git repository, flyspray is slow developing (if still does it).
We need to review and see what items there need to be migrated ...
Can be done later, but if anyone wants to start, he/she is welcome.
Cheers, Daniel
On 09/12/14 21:01, Victor Seva wrote:
On 12/08/2014 09:44 AM, Daniel-Constantin Mierla wrote:
Considering all above, I propose to stop committing togit.sip-router.org and pushing to github starting either next Monday (Dec 15) (or Wednesday (Dec 17) if not ready by Monday). Existing developers have to send me the github username to add it to kamailio project.
Are we going to use the github issues instead of our flyspray? Do we need to migrate open issues to github then?
Cheers, Victor
sr-dev mailing listsr-dev@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
-- Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Hi Daniel,
If you want I can migrate old issues to github without problems.
My idea, keep in labels the version,category, and add as normal the reporter, title, body, comments.
Regards.
2014-12-09 21:57 GMT+00:00 Daniel-Constantin Mierla miconda@gmail.com:
I am for using github -- besides it will integrate better with git repository, flyspray is slow developing (if still does it).
We need to review and see what items there need to be migrated ...
Can be done later, but if anyone wants to start, he/she is welcome.
Cheers, Daniel
On 09/12/14 21:01, Victor Seva wrote:
On 12/08/2014 09:44 AM, Daniel-Constantin Mierla wrote:
Considering all above, I propose to stop committing togit.sip-router.org and pushing to github starting either next Monday (Dec 15) (or Wednesday (Dec 17) if not ready by Monday). Existing developers have to send me the github username to add it to kamailio project.
Are we going to use the github issues instead of our flyspray? Do we need to migrate open issues to github then?
Cheers, Victor
sr-dev mailing listsr-dev@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
-- Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Hello,
an update on this topic: the gitweb was deployed and the read-only cloning from kamailio.org mirror repository is ready. Therefore I plan to point git.sip-router.org to it on Monday, Dec 15, around noon (GMT).
I will send a notification before the procedure is started and another one when it is finished. No commit should be pushed in between (no matter what branch). After that, new commits must be pushed to github.
As an user that cloned from git.sip-router.org, pulling/fetching for updates should just work afterwards.
As a developer, you must change the remote URL (or make a new clone from github). If you are currently a developer with write access to git.sip-router.org repository and you haven't sent yet the github user id, do it as soon as possible, specially if you have commits to do in the near future.
Cheers, Daniel
On 08/12/14 09:44, Daniel-Constantin Mierla wrote:
Hello,
I setup the mirror of Kamailio github repository to kamailio.org, can be seen online at:
Mirroring is triggered by a push to github, so it is pretty much in real time.
Right now the commit and mirroring flow is:
- commit to git.sip-router.org triggers mirroring (push) to github,
which triggers a mirroring (fetch) on git.kamailio.org
Practically with a commit pushed directly to github, the first part of the above is skipped.
All seems to be ok, my last commits were done to test the mirroring including the notification emails - I will send a separate message about what we can get there.
The missing parts are the deployment of gitweb in order to have the links from archived email notifications still valid and pointing git.sip-router.org to kamailio mirror server.
Considering all above, I propose to stop committing to git.sip-router.org and pushing to github starting either next Monday (Dec 15) (or Wednesday (Dec 17) if not ready by Monday). Existing developers have to send me the github username to add it to kamailio project.
Any suggestions and comments are welcome!
Cheers, Daniel
-
Daniel-Constantin Mierla -
Eloy Coto Pereiro -
Konstantin M. -
Ovidiu Sas -
Victor Seva