Closed masatake closed 9 years ago
@masatake Is this the place to discuss the announcement that is being prepared?
First of all, I am really glad you have taken up the challenge of the much needed reactivation the development of ctags!!! I think the points you mention in the document make sense. The lack of activity drove me to this repo as well.
To answer the very first question. Yes, I think it is acceptable to use ctags-devel for this. As long as it is clear that you want to revive the project as a whole and it is not a hostile takeover. Therefore I think you should avoid the word "fork". Forking a project has a negative sound to me (think OpenOffice vs LibreOffice). Reactivation, reviving or continuation of the development or even just repository or repo sounds much better.
I think the new NEWS file you mention is very important. It must show the (main) differences between the sourceforge SVN and the repo at github. People must see how much work has been done already. It must make them curious and willing to help without the need to recruit them. (Yes, I read that pdf ;-)
If you would like this repo to become the official repo I think @fishman should consider if he wants to transfer this repo into a organization, and if so mention that intention in the announcement. See https://help.github.com/articles/how-to-transfer-a-repository
Are there any plans to "recruit" the maintainers of ctags in geany. I love to see some features of their ctags adjustments being included, like targets in makefiles and proper scopes in SQL. Or should we just backport them?
And are you aware of this repo? https://github.com/vim-jp/ctags/ There is some activity there as well. Most comments are in Japanese, which I don't understand.
As I said: just points to discuss. Keep up the great work!
@ffes yeah i have thought about it. an organization would definitely be a good idea especially given that i can't make private feature branches for pull requests currently.
we actually had the geany maintainer contribute a new php parser. so yes, it's on the list. They have a rust parser too.
Thank you for comments. I'm writing NEWS file.
Situation we are in:
I think our team is still weak to do massive recruiting attack. The result of development after forking is not enough, too.
Any kind of pull requests are welcome.
However, If you are interested in fishman development in long term, I would like you to help the project in following aspects, way:
I have updated NEWS.fishman. Some of important features we added are written. I need proof-readers:-)
I decide not making single big announcement. In stead doing small incrementally at multiple places.
More comprehensive TRAKCING file is needed.