Updates tagged with gitorious on Hacker Poesy!
lnxw48: @chimo Where did you move your GS plugins repo? https://fresh.federati.net/url/3501 still says your plugins are hosted on #gitorious. #code-hosting #git !gnusocial
lnxw48's status on Thursday, 11-Jun-2015 03:31:58 EDT
@chimo Where did you move your GS plugins repo? https://fresh.federati.net/url/3501 still says your plugins are hosted on #gitorious. #code-hosting #git !gnusocial
mmn: I believe @knuthollund wrote a plugin for this. I haven't analyzed and pushed the code yet to the main repo, but I believe it works for him :) You should be able to put it in your 'local/plugins/' folder. I think he moved the repo from #Gitorious but I'm not sure where right now.
mmn's status on Thursday, 30-Apr-2015 05:06:25 EDT
I believe @knuthollund wrote a plugin for this. I haven't analyzed and pushed the code yet to the main repo, but I believe it works for him :) You should be able to put it in your 'local/plugins/' folder. I think he moved the repo from #Gitorious but I'm not sure where right now.
mmn: @roland do you want to take over the maintenance of #Gitorious source code? I don't. And running discontinued software doesn't sound very fun.
mmn's status on Friday, 13-Mar-2015 14:48:42 EDT
@roland do you want to take over the maintenance of #Gitorious source code? I don't. And running discontinued software doesn't sound very fun.
mmn: Since the #Gitorious code is being discontinued (afaik), and I haven't seen a community uptake on it, it would mean using code that is unlikely to get updates. I doubt any of us involved on our spare time with #GNUsocial have the capacity to overtake responsibility for the source code. Alternatives we have been looking at however are http://status.hackerposse.com/url/ https://social.umeahackerspace.se/notice/199740
mmn's status on Thursday, 12-Mar-2015 19:45:20 EDT
Since the #Gitorious code is being discontinued (afaik), and I haven't seen a community uptake on it, it would mean using code that is unlikely to get updates. I doubt any of us involved on our spare time with #GNUsocial have the capacity to overtake responsibility for the source code. Alternatives we have been looking at however are http://status.hackerposse.com/url/…
mmn: (because #Gitorious is closing down because proprietary #GitLab are taking over)
mmn's status on Thursday, 12-Mar-2015 18:35:25 EDT
(because #Gitorious is closing down because proprietary #GitLab are taking over)
rozzin: @lnxw48 @jezra, it seems that #gitorious' "git://" repo URLs no longer work, but the equivalent HTTP & HTTPS URLs do.
rozzin's status on Tuesday, 10-Mar-2015 17:55:52 EDT
@lnxw48 @jezra, it seems that #gitorious' "git://" repo URLs no longer work, but the equivalent HTTP & HTTPS URLs do.
lnxw48: @jezra There are a few others I've seen having trouble reaching the !gnusocial #gitorious repo.
lnxw48's status on Monday, 09-Mar-2015 22:37:45 EDT
@jezra There are a few others I've seen having trouble reaching the !gnusocial #gitorious repo.
mmn: Apparently I didn't read it close enough though, it wasn't #Gitorious data they were moving. I made an ass of myself through assuming!
mmn's status on Monday, 09-Mar-2015 16:34:42 EDT
Apparently I didn't read it close enough though, it wasn't #Gitorious data they were moving. I made an ass of myself through assuming!
mmn: Regarding #GitLab moving #Gitorious data to their own servers using obscure, repeatedly failing solutions over simply rsync'ing (as they likely want to integrity check all the transferred files anyway ffs!): "<TakinOver> Their procedure just seems terribly ad-hoc. That article should scare the sh*t out of the leaders of any project or organization that is considering G https://social.umeahackerspace.se/notice/198468
mmn's status on Monday, 09-Mar-2015 15:50:22 EDT
Regarding #GitLab moving #Gitorious data to their own servers using obscure, repeatedly failing solutions over simply rsync'ing (as they likely want to integrity check all the transferred files anyway ffs!): "<TakinOver> Their procedure just seems terribly ad-hoc. That article should scare the sh*t out of the leaders of any project or organization that is considering G…
mmn: What's awesome with #Gitorious is that it's #AGPL. So it's copyleft, not just libre.
mmn's status on Tuesday, 03-Mar-2015 19:01:29 EST
What's awesome with #Gitorious is that it's #AGPL. So it's copyleft, not just libre.
mmn: If you create your own branch and send a merge request on #Gitorious we can start looking it at it!
mmn's status on Tuesday, 10-Feb-2015 12:53:03 EST
If you create your own branch and send a merge request on #Gitorious we can start looking it at it!
mmn: It'd be much easier to accept it anyway if you made it as a merge request on #Gitorious.
mmn's status on Tuesday, 10-Feb-2015 03:48:29 EST
It'd be much easier to accept it anyway if you made it as a merge request on #Gitorious.
mmn: https://gitorious.org/ - even licensed AGPL and hosting several large projects already :) Since git is decentralized, the least people can do is to start a mirror repository on another server. In !gnusocial's case @mattl has set up a mirror on #github but our main repo (where merge requests are accepted) is on #Gitorious.
mmn's status on Monday, 09-Feb-2015 15:24:14 EST
https://gitorious.org/ - even licensed AGPL and hosting several large projects already :) Since git is decentralized, the least people can do is to start a mirror repository on another server. In !gnusocial's case @mattl has set up a mirror on #github but our main repo (where merge requests are accepted) is on #Gitorious.
mmn: @hannes2peer I could use my OpenID with #Gitorious when running latest !Qvitter :D I should try again later when I feel like emptying all my browser history as well, so it's not just some cookie/session thing that worked (though I _had_ logged out from Gitorious).
mmn's status on Sunday, 08-Feb-2015 08:35:37 EST
@hannes2peer I could use my OpenID with #Gitorious when running latest !Qvitter :D I should try again later when I feel like emptying all my browser history as well, so it's not just some cookie/session thing that worked (though I _had_ logged out from Gitorious).
mmn: #Gitorious supports #OpenID <3 Fucking shitpiss #GitHub doesn't.
mmn's status on Sunday, 08-Feb-2015 07:51:31 EST
#Gitorious supports #OpenID <3 Fucking shitpiss #GitHub doesn't.
mmn: For anyone who wants to know when new patches arrive at #gitorious for !gnusocial - and don't have any other RSS reader than the they read this message in - follow @gnusocialgit !
mmn's status on Thursday, 22-Jan-2015 07:49:00 EST
For anyone who wants to know when new patches arrive at #gitorious for !gnusocial - and don't have any other RSS reader than the they read this message in - follow @gnusocialgit !
mmn: Maybe we can patch #Gitorious - it is AGPL after all .)
mmn's status on Thursday, 22-Jan-2015 03:53:14 EST
Maybe we can patch #Gitorious - it is AGPL after all .)
mmn: @sazius @stigatle I'd prefer having something to link people to that's not a #gitorious repo though. A simple, trustworthy "download yaics here" would be fine (hosted wherever, on stigatle's personal website or whatever). Having a git archive of the binaries is also good for posterity and is probably of interest for digital historians in the future ;)
mmn's status on Wednesday, 21-Jan-2015 09:16:03 EST
@sazius @stigatle I'd prefer having something to link people to that's not a #gitorious repo though. A simple, trustworthy "download yaics here" would be fine (hosted wherever, on stigatle's personal website or whatever). Having a git archive of the binaries is also good for posterity and is probably of interest for digital historians in the future ;)
mmn: Except we prefer #Gitorious which is AGPL licensed ;) https://gitorious.org/social/mainline/source/nightly
mmn's status on Friday, 16-Jan-2015 17:38:02 EST
Except we prefer #Gitorious which is AGPL licensed ;) https://gitorious.org/social/mainline/source/nightly
rozzin: Looks like #gitorious just doesn't escape angle-brackets in commit-message texts. #Joy.
rozzin's status on Sunday, 12-Jan-2014 15:21:33 EST
Looks like #gitorious just doesn't escape angle-brackets in commit-message texts. #Joy.
erkanyilmaz: me neither, I like #gitorious https://en.wikipedia.org/wiki/Gitorious
erkanyilmaz's status on Sunday, 12-Jan-2014 14:22:47 EST
me neither, I like #gitorious https://en.wikipedia.org/wiki/Gitorious
larjona: Cada forja de #softwarelibre tiene sus ventajas, pero entre #Github, #Bitbucket o #Gitorious, sólo Gitorious tiene licencia libre (#AGPL)
larjona's status on Friday, 05-Apr-2013 11:36:57 EDT
Cada forja de #softwarelibre tiene sus ventajas, pero entre #Github, #Bitbucket o #Gitorious, sólo Gitorious tiene licencia libre (#AGPL)
zack: @fontana and besides, there is no federation support whatsoever in #gitorious . No real progress toward being #autonomous
zack's status on Sunday, 10-Feb-2013 05:25:39 EST
@fontana and besides, there is no federation support whatsoever in #gitorious . No real progress toward being #autonomous
zack: RT @fontana @bkuhn @pchestek tried to use #Gitorious but gave up but was able to use #github. Something significant in that.
zack's status on Friday, 08-Feb-2013 09:49:54 EST
RT @fontana @bkuhn @pchestek tried to use #Gitorious but gave up but was able to use #github. Something significant in that.
fontana: @bkuhn @pchestek tried to use #Gitorious but gave up but was able to use #github. Something significant in that.
fontana's status on Thursday, 07-Feb-2013 21:37:49 EST
@bkuhn @pchestek tried to use #Gitorious but gave up but was able to use #github. Something significant in that.
rozzin: Oh, I see: repo-names on #Gitorious need to be globally unique. I guess the `user→project→repo' indirection exists just to be a #PITA, then?
rozzin's status on Sunday, 29-Jul-2012 19:04:42 EDT
Oh, I see: repo-names on #Gitorious need to be globally unique. I guess the `user→project→repo' indirection exists just to be a #PITA, then?
rozzin: I don't get #gitorious' `user→project→repo→branch' layering: why are multiple #git *repostories* *per project* *per developer* useful?
rozzin's status on Sunday, 29-Jul-2012 15:30:38 EDT
I don't get #gitorious' `user→project→repo→branch' layering: why are multiple #git *repostories* *per project* *per developer* useful?
zack: it depends on the kind of discussions you've in mind. You can comment on commits on #Gitorious too, e.g. http://ur1.ca/9qqte
zack's status on Saturday, 07-Jul-2012 13:35:34 EDT
it depends on the kind of discussions you've in mind. You can comment on commits on #Gitorious too, e.g. http://ur1.ca/9qqte
zack: RT @fontana Decided to adopt @bkuhn's recommendation to use #Gitorious in connection with development of #GPL.next. http://ur1.ca/9qq86
zack's status on Saturday, 07-Jul-2012 12:00:29 EDT
RT @fontana Decided to adopt @bkuhn's recommendation to use #Gitorious in connection with development of #GPL.next. http://ur1.ca/9qq86
fontana: Decided to adopt @bkuhn's recommendation to use #Gitorious in connection with development of #GPL.next. http://ur1.ca/9qq86
fontana's status on Saturday, 07-Jul-2012 11:21:01 EDT
Decided to adopt @bkuhn's recommendation to use #Gitorious in connection with development of #GPL.next. http://ur1.ca/9qq86
jpope: Still learning how to git via #gitorious. Do (or should) merge requests get (be) closed after being merged? If so, how do I do so?
jpope's status on Wednesday, 30-May-2012 20:43:56 EDT
Still learning how to git via #gitorious. Do (or should) merge requests get (be) closed after being merged? If so, how do I do so?