Perl 6 - the future is here, just unevenly distributed

IRC log for #darcs, 2016-09-14

| Channels | #darcs index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:00 mizu_no_oto joined #darcs
01:11 Big_G joined #darcs
01:47 ilbot3 joined #darcs
01:47 Topic for #darcs is now http://darcs.net/ | logs: http://irclog.perlgeek.de/darcs/ | darcs 2.12.1 is out http://darcs.net/Releases/2.12
11:04 mizu_no_oto joined #darcs
13:06 Big_G joined #darcs
14:38 stulli joined #darcs
14:40 gh_ joined #darcs
14:44 gh_ Heffalump, I don't think changing the question will do. Registered spam users will still be able to edit, right?
14:44 * gh_ obliterates +130 spam patches again
14:52 Riastradh joined #darcs
14:56 gh_ I did a 2.12.4 release that should really fix compiling for Windows
15:24 sm nice gh_
15:25 sm what do you think about the appveyor idea
15:29 gh_ sm, I like it, in fact I think that in spite of the caveats, we should have someday github mirrors for our repositories
15:30 gh_ I mean, screened, reviewed and branch-x.xx
15:34 sm the git way would be to have them as branches
15:35 sm do we know how to mirror darcs repos to git branches ? sounds not hard
15:35 gh_ hmm currently darcs does not provide this
15:35 gh_ I mean the built-in `darcs convert export` command
15:36 gh_ so I'd rather have git mirrors "the darcs way" , i.e., 1 repo = 1 branch
15:36 sm wow, I wouldn't. Seems like even more proliferation
15:37 gh_ or maybe we could choose to only have a mirror for the current release branch
15:38 gh_ but after a while without any release, we will also want to have feedback on the screened branch
15:39 gh_ (assuming having mirrors on github would bring feedback)
15:40 sm it/they would bring feedback from appveyor, travis too
15:41 sm might eventually save you some work as release manager ?
15:41 sm appveyor generates windows binaries, for example
15:41 gh_ yeah, I also mean feedback in the sense of having people submitting pull requests
15:42 sm that would be great, except how would the darcs project handle that :)
15:42 sm pull requests for darcs, on github.
15:42 * sm 's brain explodes
15:45 sm thought experiment: move darcs development entirely to github. Embrace the best available tooling to develop darcs faster and more comfortably
15:47 sm horrible thought isn't it :)
15:47 sm it probably would be more efficient though
15:57 gh_ sm, we would handle it manually at first, if the contributions are worth it
16:00 gh_ it would be only a way for the project to have more input
16:47 Big_G joined #darcs
17:15 Riastradh joined #darcs
22:30 mizu_no_oto joined #darcs

| Channels | #darcs index | Today | | Search | Google Search | Plain-Text | summary