-
Notifications
You must be signed in to change notification settings - Fork 29
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
Still being maintained? #52
Comments
Carl, that would be amazing. We can make you the official maintainer. It would be nice to also set up an automated email that gets sent out to people that have subscribed to the list. |
We've been pretty swamped lately and had zero time to carry the weight of improving/maintaining this super important Public asset. |
Sure, this actually very much falls in line with some academic research on municipal purchasing/smart city principals I’ve been working on lately, as well as my work as a Brigade Captain for Code for America.
Procurement data standards are all over the place, and some attempt at standardization would be at least headed in the right direction.
I can set up the automated email, no problem.
Just let me know the details for the subscriber list and such. I’m confident working with Middleman so that shouldn’t be an issue either.
CVL
… On Mar 16, 2017, at 1:23 PM, Alan Mond ***@***.***> wrote:
Carl, that would be amazing. We can make you the official maintainer. It would be nice to also set up an automated email that gets sent out to people that have subscribed to the list.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#52 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABnnIVxWY9Gfa7nl9k3fvZ0qP0DYMxkOks5rmXAYgaJpZM4MfnT->.
|
Great. Going to tag this as civic-tech project seeking contributors to the Code for America network as well if that’s okay. Obviously can’t commit a huge amount of time myself, but will do my best.
And just for purposes of clarity, after significant additions/improvements are made, is it okay to update the README.md to say something along the lines of “A project originally conceived and built by MuniRent and <insert current contribs names here>. Project currently maintained by <Open Savannah> and the <Code for America> brigade network, along with <insert future contribs names here>”?
That’s jumping the gun obviously, but don’t want to give any appearance of hijacking MuniRent’s project and want to be clear that it’s not something we started just by ourselves.
… On Mar 16, 2017, at 1:56 PM, Alan Mond ***@***.***> wrote:
Carl, just granted administrator rights to OpenProcure repo. Thanks for keeping the lights going on this project. Will reach out via email about subscriber list.
<https://cloud.githubusercontent.com/assets/1726205/24011126/185186ae-0a37-11e7-8844-b9294edc853e.png>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#52 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABnnISF-2qdMDn3zd9whYEpI03M8w17Tks5rmXfLgaJpZM4MfnT->.
|
Yes, definitely ok to tag as CfA project. We are part of the CfA family (MuniRent is a CfA accelerator alumni) so go for it! It would be good to add specific tags to issues so people can easily start contributing. re: attribution plan after significant additions/improvements => 👍 |
While I recognize this project is far from comprehensive, it's definitely a step in the right direction for a very real problem, especially after having spoken in recent months to a number of municipal governments.
I notice the project has been stagnant for a while. Do you all plan to continue any work with it? If not, I will gladly volunteer to help maintain it if you all don't have the time/resources. Just let me know.
The text was updated successfully, but these errors were encountered: