Talk:Source Code

From WineHQ Wiki
Revision as of 12:55, 11 March 2016 by KyleAuble (talk | contribs)
Jump to: navigation, search

Consolidating Repos?

Maybe this discussion belongs on the mailing list (we can always move it there), but it's more of a meta-question. I've gone through and updated the page; e.g. all the old cvs commits have been merged into the git tree and the cvs server powered down (very nice). But some of the code related to the project is still scattered about or... of unclear provenance? I'm just looking for clarification on a few things, but beyond just updating this page, I wonder if we could reorganize the repos themselves.

Specifically, I'm wondering about...

  • The new wiki: I'm not clear on if it even needs its own code, or is it all MediaWiki and general WineHQ theming (Jeremy?) If it does have some custom code, can we add that to the WineHQ git server? And if not, should we write up a quick how-to on mirroring somewhere?
  • Sourceforge: I know we were trying to move away from it some, but that consolidation hasn't been finished in a few ways...
    • It still appears to be the go-to place for Slackware packages. If that's the packager's preference, let's not fix what ain't broken, but perhaps we could offer those for download on WineHQ or somewhere else? I can email Simone myself to ask at some point.
    • I can see the value in still uploading the source packages, especially if the Slackware packages stay there too, but is there a reason to keep the other old files and packages? Or is that a dumb question and what's uploaded on sourceforge stays on sourceforge?
    • The wine-gecko git repo there seems alive & well (is that the upstream repo?), but there are long-abandoned mirrors of the wine and wine-test-bot code.
    • Finally, CVS is still turned on there even though it's been mostly cleared out. All that's left is an empty folder for docs and an outdated version of the old wiki code
  • winezeug: Even though it's mostly abandoned and I don't think it qualifies as part of the Wine project proper, I thought it was worth including. It would probably be good if someone with a better idea of what's still useful and what's been superseded decided how to treat it on the wiki. -- KyleAuble (talk) 15:05, 27 February 2016 (CST)

I'd ask Jeremy about the wiki code, and take the questions about Sourceforge to wine-devel. As for winezeug, personally I wouldn't link to a repo that hasn't been updated in 4 years. If it's ever revived, it can be added then. --RosanneDiMesio (talk) 16:47, 27 February 2016 (CST)

I just sent an email to the mailing list, but you're probably right about winezeug. Even if it turns out to be worth linking to, it may belong more on another page. I guess it really depends on how much of it's totally obsolete or worth recovering; I'll change it up once I know if anyone has plans for it. -- KyleAuble (talk) 20:49, 28 February 2016 (CST)
I helped Dan maintain it originally. Some of it is still useful. There's a fork of it on my github, and some others have forked it as well. It may be more useful if some of the old stuff were removed or if it were moved to another repo though. Austin987 (talk) 20:49, 28 February 2016 (CST)
I went ahead and moved it from here to its own small page on the wiki for now, plus forked it on my Bitbucket account. If I've got nothing else to do at some point in the next few months, I'll go through it some. -- KyleAuble (talk) 22:47, 1 March 2016 (CST)

After a little more asking around, I'm still not completely sure about the wiki but pretty confident it doesn't have any custom code. If anyone ever shows interest in mirroring (which might require building on the existing MediaWiki extensions), we can hash that out on wine-devel. -- KyleAuble (talk) 12:55, 11 March 2016 (CST)