Skip to content
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

Add app credits page #1795

Open
m4gr3d opened this issue Aug 21, 2016 · 6 comments
Open

Add app credits page #1795

m4gr3d opened this issue Aug 21, 2016 · 6 comments
Labels
Milestone

Comments

@m4gr3d
Copy link
Member

m4gr3d commented Aug 21, 2016

Add a page crediting the community developers.
Maybe allow users to contact the devs directly from that page (i.e: via email address for custom dev?).

@m4gr3d m4gr3d added the Feature label Aug 21, 2016
@m4gr3d m4gr3d added this to the Tower v4.1.0 milestone Aug 21, 2016
@m4gr3d
Copy link
Member Author

m4gr3d commented Aug 21, 2016

@DroidPlanner/dev @DroidPlanner/lead-devs @DroidPlanner/maintainers Thoughts on this?

@kellyschrock
Copy link
Contributor

Sounds good to me if it's good with everyone else.

@squilter
Copy link
Member

Sure. I'm not sure if email addresses would be helpful. How will a user know who to email regarding a particular feature?

@kellyschrock
Copy link
Contributor

That's a good question. What if, in the contributors list, there was a
little blurb about what they've worked on? It would be an extra maintenance
item.

On Sun, Aug 21, 2016 at 7:54 PM, Sebastian Quilter <notifications@github.com

wrote:

Sure. I'm not sure if email addresses would be helpful. How will a user
know who to email regarding a particular feature?


You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
#1795 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADmhzZ9ScUzdoIcC4evfF9wpZFtd41b9ks5qiPNagaJpZM4JpXFv
.

@m4gr3d
Copy link
Member Author

m4gr3d commented Aug 22, 2016

@kellyschrock @squilter The idea is to break down the credits page in several sub-sections (i.e: General, Map, Translations, Core Lib, etc) with each having the list of the devs that contributed to it.

With regard to the maintenance, each interested dev would submit a pr to include himself/herself within the credits page. As such the maintenance should be minimal and mostly consist in reviewing the dev's pr for inclusion.

@kellyschrock
Copy link
Contributor

Sounds like the best way to do it. I was going to suggest having the
contributing developers maintaining their section of this document to
minimize overhead, actually.

On Mon, Aug 22, 2016 at 3:12 AM, Fredia Huya-Kouadio <
notifications@github.com> wrote:

@kellyschrock https://github.com/kellyschrock @squilter
https://github.com/squilter The idea is to break down the credits page
in several sub-sections (i.e: General, Map, Translations, Core Lib, etc)
with each having the list of the devs that contributed to it.

With regard to the maintenance, each interested dev would submit a pr to
include himself/herself within the credits page. As such the maintenance
should be minimal and mostly consist in reviewing the dev's pr for
inclusion.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1795 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADmhzVySAIfWQilUhf2jg-G_0gB2AIuSks5qiVnsgaJpZM4JpXFv
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants