New version of g3data

[whit2333]

I have add error bar extraction on my fork at https://github.com/whit2333/g3data .
This branch does not seem to be maintained or under any sort of development.
I have contacted the original author (Jonas Frantz) who says that Paul Novak (pn2200) is the maintainer. What is the status of mainainership?

[impaktor]

try to submit a pull request for the feature and see if something happens.

[Phyks]

Hi,

I'm interested in adding an auto-extract feature. Any update about the current maintainership status ? (@whit2333 ?)

Is there any maintained forks if this is not updated anymore ?

[whit2333]

Hi,
An auto-extract feature would be great! I think I have been the only one to do anything in the past 3 years or so. I am not sure pn2200 does anything anymore, he is certainly not reading this. I suppose I will submit a pull request but I would encourage you to start from my fork, which has error bar extraction.

[Phyks]

Ok for the fork. I was wondering which one was the most uptodate. I think I will start from your fork then. I'm not sure to manage to end up with something usable, but I'll let you know.

Maybe if your fork is definitely the maintained one it could be nice to add some reference somewhere, because I found this repo directly when I looked for g3data.

[whit2333]

Ok. I would be interested in your features. Let's move the conversation over to my fork.

[Phyks]

Ok, but as a fork, issues are closed on it…

[Phyks]

Any news on the status of the project ?

[whit2333]

Nope. You can checkout my branch if you want to start from something updated.

Cheers,
Whit

On Tue, Jul 01, 2014 at 11:10:55AM -0700, Lucas Verney wrote:

Any news on the status of the project ?

---

Reply to this email directly or view it on GitHub:
#3 (comment)

[Phyks]

@whit2333 : Ok. In this case, maybe it would be better to transform your repo to a real repo, and not a fork, so that users could open issues on it ? It's a bit weird to comment here some relatively different version…

[bilderbuchi]

no need to transform repos, issue tracking can simply be switched on in the repo settings.

[whit2333]

Ok, I enabled issues in my repo.