mjbeverley / inxi

Automatically exported from code.google.com/p/inxi
0 stars 0 forks source link

Move code to Github #67

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
When you move inxi code to Github?

Original issue reported on code.google.com by vasc...@gmail.com on 25 Mar 2015 at 6:58

GoogleCodeExporter commented 9 years ago
When? and why github? a for profit non free resource that might disappear any 
day just like the flakes here at googlecode are going to disappear? I was and 
am profoundly disappointed that googlecode just turns itself off because they 
don't have the attention span to run the resource they built to help pay back 
the free software community, but I guess google is so big now that they don't 
feel any need to repay such debts, even though their entire system is built on 
foss.

With that said, inxi probably will move to github merely because it's the 
'popular choice', though it's not decided yet. Not that it matters where inxi 
source repos are hosted, it's not like it has a lot of source code files, so 
anyone who wants to work on it who can't figure out how to download a file 
probably shouldn't be working on it in the first place, given it's complexity 
internally.

github was totally out of the question before because it didn't handle svn, but 
they now apparently have an svn shiv working, so it's now thinkable. git is 
totally and completely incompatible with my coding work flow, but if I can 
interact with it using svn I don't care that much.

The bottom line is that in the real world, actually moving stuff like this 
project takes at least one (unpaid and totally wasted) day, sometimes 2, 
depends on what issues you hit, for example, I'm told the wiki import isn't 
working reliably, and I doubt the issues will transfer.

I actually don't want to have inxi use a second party source at all for stuff 
like wiki and issues because now that googlecode has flaked out on its implicit 
obligation to be a reliable code repo hoster, I certainly do not trust a small 
company with probably a very weak business model like github to be any more 
reliable, even if it happens to be today's fad, just like sourceforge was the 
fad before googlecode, but people don't have very good memories and believe 
that the present is fundamentally different from the past. I don't share this 
belief, I tend to believe that trends continue, so I fully expect github to 
become as foul as sourceforge has become, or as flaky as googlecode in terms of 
just stopping, or stopping free hosting of projects.

Since inxi has until august to fully move, I'm personally certainly not in any 
hurry. I'm leaning towards never trusting a hosted repo again houwever for 
wiki, I'm going to look into the options, it's probably best to connect issues 
with the source repo, but I'm not going to trust the site documentation to a 
non free for profit site again, we'll probably put that on inxi.org and make it 
a standalone site, that's a better way to handle things long term, same as I do 
already for smxi.org, a site that never fails and never goes down and never is 
hit by a flakey source host deciding they can't be bothered to do their jobs 
anymore because they don't feel like it, and can't handle spamming and 
spammers, a problem google has always had, lol, in every part of their 
business, not being able to handle spammers,

Original comment by inxi-...@techpatterns.com on 25 Mar 2015 at 6:10

GoogleCodeExporter commented 9 years ago
Thanks for wide reply.
I say Github because Google recommend it (even present button Export to 
Github). And git is really comfortable for me (and Github too).

However I'll take any of your choice. I'm just worried about the fate of inxi 
host place.

P.S. I am maintainer of inxi package for Fedora and EPEL.

Original comment by vasc...@gmail.com on 25 Mar 2015 at 6:20

GoogleCodeExporter commented 9 years ago
As the maintainer of a top flight FREE software distribution, that is well 
known for its commitment to free software, free as in freedom, not price, I 
would suggest you feel a little less love for the radically non free github 
even though it sadly has become the current fad for source hosting. I am 
actually very sad that a truly free and open source hosting solution isn't 
available, only these stupid businesses that will in the end screw over their 
users in one way or the other, like sourceforge and now googlecode are doing.

I'm also actually worried about the fate of inxi source hosting because I hate 
the choices I have, they are in my opinion all bad. That's why I originally 
picked googlecode, I felt, obviously foolishly, that I could trust a massive  
company, with huge budget, to be able to reliably host source code over a long 
time. Given they failed inxi, I have no reason at all to believe that github 
will do any better over time, yet I do not want to move source hosting every 
time the web decides to follow a new fad, it's a pain and takes a lot of time 
and work and it's not fun.

You however do not need to feel ANY concern about inxi source hosting, it will 
be hosted somewhere, the requirements are not complicated, the hosting place 
should be free, it should not be non free proprietary, it should have issue 
tracking.

I may use debian's stuff, though I haven't decided, it's not as nice but in a 
way I don't care, if I can find a permanent free solution that is better than a 
short term non free one. I really wish all these 'free' software projects would 
consider this more.

Original comment by inxi-...@techpatterns.com on 25 Mar 2015 at 7:51

GoogleCodeExporter commented 9 years ago
The main, and in my opinion, only, advantage of github is that is today hugely 
popular, like sourceforge used to be, so the odds of patches flowing in are 
slightly higher, but I've found top end users and maintainers tend to be the 
best sources of patches anyway. This is a real advantage note, even though 
github is proprietary and non free, and is a business as far as I know, ie, 
it's a bad choice for reliable long term hosting of code, but it's a good 
choice for maximizing code exposure because web users tend to just blindly 
follow the current fad with little thought about the consequences of that long 
term. 

However, I'm busy at the moment and don't have time to deal with the headaches, 
though I may switch the wiki pages to a simple html site version, we've never 
gotten a single wiki edit request that I can remember beyond noting bugs in the 
documenation, so it's not like we'll lose anything we didn't have need for in 
the first place. I'll talk to the inxi co dev trash80 about it, he runs the 
domain name, and we might as well leverage it mpre than we have.

Original comment by inxi-...@techpatterns.com on 25 Mar 2015 at 8:27

GoogleCodeExporter commented 9 years ago
By the way, inxi project welcomes suggestions about anywhere that is not in 
fact a bad option, so far all the options I have looked at are bad, for one 
reason or another. I am leaning towards finding an svn solution because I 
frankly dislike git, though I would use git for projects I don't really care 
about and which are simpler than inxi.

I had no complaint with googlecode hosting at all, it worked, it was simple, 
and it let me do what I wanted in the way I wanted, which is why it pisses me 
off that they are shutting it down, it's actually hard to replace it. github is 
NOT a replacement in my opinion, it's just a totally different way of doing 
things.

Original comment by inxi-...@techpatterns.com on 26 Mar 2015 at 12:46