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

Switch stipend proposals to git based and/or db storage. #51

Open
starbelly opened this issue Mar 8, 2021 · 8 comments
Open

Switch stipend proposals to git based and/or db storage. #51

starbelly opened this issue Mar 8, 2021 · 8 comments
Labels
need more info when a issue need more explanations website issues/ideas related to website

Comments

@starbelly
Copy link
Member

Currently stipend proposals go to email. This should be changed so that they go to a private repository or into the database.

We had initially talked about it going to a private git repo, and I suppose it still can, but the data also has to go into the database. We are not able to create reports, etc right now and if we simply putting them in a git repo, we will still have that problem.

@starbelly starbelly changed the title Switch stipend proposals to git based or db storage. Switch stipend proposals to git based and/or db storage. Mar 8, 2021
@benoitc
Copy link
Collaborator

benoitc commented Mar 15, 2021

How having the data in the database helps to create report? One point of having content is github is that we can easily share it with others.

@benoitc benoitc added website issues/ideas related to website need more info when a issue need more explanations labels Mar 15, 2021
@starbelly
Copy link
Member Author

How do we sanely extract the numbers as an example?

@benoitc
Copy link
Collaborator

benoitc commented Mar 15, 2021

do we need to extract the number programatically? For which usage?

Right now stipends are handled by people that actually forward them by mail and discuss over mail about it. I am not sure we need more at the moment. Have there been any request about it yet?

@starbelly
Copy link
Member Author

Yes, this came up via sponsorship wg, perhaps @peerst can comment on this.

@starbelly
Copy link
Member Author

@benoitc How about we have the best of both worlds like we do with board reports? That is, structured form of proposal goes into the database, but also a markdown version of the proposal gets opened as a PR on a private repo?

@peerst
Copy link
Member

peerst commented Mar 30, 2021

Not really fond of the everything is done via Github if it works or not.

@peerst
Copy link
Member

peerst commented Mar 30, 2021

Why e.g. not handle stipend emails with e.g.Trello? In embedded WG we use Trello to develop our stipend proposals. Look which WG is actually doing something in development proposal...

Development cost = 0

Trello boards can be emailed forwarded to (built in) and then proposals can be brought through a flexibly definable process.

@starbelly
Copy link
Member Author

I am open to trello myself. I know we discussed this option before and I think the concern was more tooling, but for internal purposes and really at the board level, I think it could be fine.

I do think regardless of whether it is trello or github, the data should still go in the database. Can we compromise one that setup before discussing trello vs github?

In other words, can we agree that the data should go into the db AND also make use of trello or github for conversational purposes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need more info when a issue need more explanations website issues/ideas related to website
Projects
None yet
Development

No branches or pull requests

3 participants