-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Voting on Features #5
Comments
@ejmr I may not be able to realize all the requests, but I would like to know the demand of users. |
I do not seem to be able to see badges from my environment. If it becomes visible after tomorrow, it applies to other projects as well. |
I knew you would be a great maintainer, and that statement proves it. I think that I am going to try to contribute again---I've decide I woud like to publish more code before I die sometime in the next eighteen months. And one of the major reasons I am compelled to contribute once again is because of your talent as a manatiner. PHP Mode is in great hands, and I couldn't be happier with your work.
|
@zonuexe You're the best man, I love how much you've contributed to the state of PHP on Emacs. Emacs has made me get into open source, but it's stuff like PHP-suite that encourages me to master elisp. |
@jonnycyr Yeah, creating @emacs-php and moving multiple PHP modules for GNU Emacs into one place might be the best thing @zonuexe has done yet. It is certainly a fantastic idea which I never thought of once during my six years as the maintainer. I love how quickly Usami as the maintainer organized everything.
|
This patch updates both READMEs with a mention of the official FeatHub page for the GNU Emacs PHP Suite. It is highly likely that users will continue to request features via GitHub itself. However, since we discussed using FeatHub (see link below) we need to let users know that it exists. If we do not then, obviously, no one will use it. The changes do not describe exactly *how* users should make requests through FeatHub because we currently have no defined workflow involving FeatHub. In fact, it is not even certain that we will end up using FeatHub at all; eventually we may very well prefer that users continue to make feature requests through GitHub's mechanisms. But we cannot accurately judge the merits of FeatHub if no one is aware it even exists. Therefore this patch is a small step towards helping us decide on the best way to collect user feedback, particularly with regard to new features people want to see in PHP Mode and its related projects. See-also: emacs-php/php-suite#5 Signed-off-by: Eric James Michael Ritz <[email protected]>
This is related to issue #2 for creating a wishlist. Does anyone here have experience using FeatHub? If so, I would greatly appreciate any opinions on it. For people like myself who have never used it, how does @emacs-php feel about potentially using FeatHub as a way to help prioritize features for PHP Mode and all related projects?
The text was updated successfully, but these errors were encountered: