mirror of
https://github.com/NarrativeScience-old/log.io.git
synced 2026-04-26 01:25:55 +03:00
[GH-ISSUE #115] Is this project dead? #93
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/log.io-NarrativeScience-old#93
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @blackrosezy on GitHub (Mar 17, 2014).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/115
46 issues and 8 pull requests, seems like not much activity from the author.
@bscott commented on GitHub (Mar 26, 2014):
been noticing the same
@bscott commented on GitHub (Mar 26, 2014):
If I had admin access, I would perform some work on it.
@romanr commented on GitHub (Mar 29, 2014):
Can anyone even build it? I spent hours on trying to get it to build. Opened issue #112
@jnovack commented on GitHub (Jul 24, 2014):
There is a fork from @muchweb with some activity on it. https://github.com/muchweb/Log.io
@jdrake @narrativecraig Can you chime in on the state of Log.IO? As this is a group, can you make other people members so that they can commit changes or make someone else an admin?
@muchweb commented on GitHub (Jul 24, 2014):
@jnovack Thanks for mentioning my branch
Apparently log.io isn't in NarrativeScience's priority project list. I was in contact with @msmathers to sort this, by eiher adding commutity maintainer and merging all progress or to progress Log.io project as a fork.
@msmathers commented on GitHub (Aug 1, 2014):
As @muchweb indicated, we have very limited resources available to maintain this project. We've just spent the past couple days addressing a handful of bugs and publishing a new NPM package, so progress is being made.
@muchweb has diligently been doing quite a bit of work on his fork, and we're looking to merge his additions into our repo as time permits. We're also looking toward bringing him in as a community maintainer so that the project's progress is not bound to our company's engineering resourcing.
@vmadman commented on GitHub (Aug 17, 2014):
+1 for all of that. I've been using log.io for about a year now, and its really fantastic. However, there are a few small things that would really help it become even more useful.
I've only just now discovered @muchweb 's fork (thanks to @jnovack) so I'm excited to see what his fork adds and improves upon.
I do hope you can bring in @muchweb -- he clearly has an ability to dedicate some time. Once the projects are synchronized I can throw in a few pull requests as well. I just wouldn't want to touch anything until the code is up-to-date.