Template lacks important information for consideration

[john-light]

In the template linked in the README file, it only specifies team member details to be included. It would be helpful to also have sections in the template for the specific deliverables, milestones, timelines, amount requested, etc that will be included in the Flock proposal.

Reference:

How to submit your proposal

• Fork the Aragon Flock GitHub repository
• Create a new directory with the team’s name inside the teams/ folder
• Inside the directory, create one file: team.md (see template), where you present the team
• Create a pull request to merge your submission into the Flock repository. In that pull request fill in all the relevant info described in the template
• Amendments to the initial proposal can be made by creating a pull request over the existent pull request for the relevant review.

The Aragon Association and representatives of the current Aragon teams will review and approve the relevant applications but the community is invited to participate in the public discussion that will take place in the comments of the relevant pull request.

[stefanobernardi]

@john-light do you think there's a need to have the team in a separate file?

I'd probably go ahead and add all of those section details in the main proposal template, and do away with the separate team folder / file.

I can get to it this week

[john-light]

@stefanobernardi I just came across this guide:

https://github.com/aragon/flock/blob/master/docs/guides/proposal.md

Which seems to have more of the sections I was expecting to find. However that guide is not linked anywhere in the README, so applicants may not know it exists unless they dig around the repo.

To your question:

do you think there's a need to have the team in a separate file?

I think it'd be fine to include the team section in the main proposal template. I can't think of a good reason for it to be a separate file.

[LouisGrx]

Hey there, I've been trying to address what was said in this issue. Here is the Fork repo where I implemented the following changes:

• Merged team.md and proposal template for simplicity purpose
• Enriched the new proposal guide.md with a bit more structure and requirements
• Updated readme.md accordingly.

Let me know how it sounds