search

area / language-latex

Syntax highlighting for LaTeX for Atom.
Other
78 stars 47 forks source link

Maintainer needed #84

Open area opened 7 years ago

area commented 7 years ago

@yudai-nkt it looks like you've made language-tex what this repo should be - would you be interested in becoming a maintainer?

yudai-nkt commented 7 years ago

@area Since the changes between language-tex and the last commit of this repo, mainly made by @yitzchak and me, has become pretty much, there might be a possibility of conflicts between my repo and the PRs in this repo (I do not check well though). Also, I don't have enough time to cope with the issues reported here, so it would be a bit hard to take over.

Apology for releasing a package based on the fork of your repo without getting permission if I should have gotten, btw.

area commented 7 years ago

No permission was needed, so no need to apologise!

I'd quite like to get this repo back into a maintained state though. Would you be against me backporting your improvements?

yudai-nkt commented 7 years ago

Would you be against me backporting your improvements?

Of course not! However, since I've never get involved in transitions of a GitHub repository, I'd like to know what I can do for you.

area commented 7 years ago

It looks like there won't be any conflicts, which is good. I think I just need to merge, and then make sure the package.json and the changelog (not necessary, but nice to have) are correct by hand.

yudai-nkt commented 7 years ago

Happy to hear that. I'd be glad if you leave PRs unmerged because there are some PRs that doesn't need to be merged for these reasons:

  1. I implemented already.
  2. I'm not too keen on merging PRs about snippets as they are quite subjective and customizable in user's snippets.cson.
yudai-nkt commented 7 years ago

@area Just to be clear for fear that my English doesn't convey my intention:

Since you told that there would be no conflicts, I'm happy to accept your offer to become a new maintainer (in this comment, I thought you wanted to import my changes and then to transfer the owership, which seems to be my misunderstanding). If you yourself are going to maintain this package again, I totally respect your decision of course.

area commented 7 years ago

Given you'd said you didn't have time to deal with the backlogs / issues, my plan was to import your changes (done, and released as 1.0.0.), then deal with all the pending PRs/issues, and then add you as a collaborator. I do want to keep a bit of a closer eye on this repo than I have been though, so I'd be aiming to pay more attention to this repo than I have been. Many hands make like work, after all!

yudai-nkt commented 7 years ago

Okay, I got it. After I was invited to a collaborator, I will release a new version of language-tex, at which the development of it is once frozen, and then work on this package!

area commented 7 years ago

I've not quite gotten to the end of the PRs and issues yet, but I've got most of them so I thought I'd add you as a collaborator now anyway :)

yudai-nkt commented 7 years ago

I've just joined, much appreciated! :+1:

Aerijo commented 7 years ago

Me too? Please? I promise I'l behave

I've also made the (comparitively smaller, arguably more versatile) language-latex2e package. I've also gone through the list of issues (my comments are everywhere), many of them can be closed either immediately or with a small patch.

yudai-nkt commented 7 years ago

Seems like I (collaborator) cannot invite the third person to a collaborator. Could you issue a collaborator invitation to @Aerijo, @area?

area commented 7 years ago

Invited. Sorry I've let this slide, been overtaken by other things at work :disappointed:

Aerijo commented 7 years ago

All good, I don't think I'll be much help in the next few weeks anyway. I can still help with issues for now though, and I'm able to close the fixed/dupilcate ones (which was one reason I wanted this).