search

fidlabs / allocator-tooling

tracking repo for allocator tooling & compliance
1 stars 0 forks source link

remove schema / id from issue template #29

Open willscott opened 5 months ago

willscott commented 5 months ago
image

none of these 3 fields are things that an inbound client will understand.

the issue->pr should auto populate them, rather than having them visible to clients

willscott commented 5 months ago
kevzak commented 5 months ago
  • the bot can automatically edit the issue to add the version field
  • the applicant should be the github user submitting the issue
  • i don't think we do anything / i don't understand what the 'Project ID' is - i think we can drop that entirely?

-Correct, bot can edit the issue to add version -The DataCap applicant field could stay. It gives the name of the github user and could be another datapoint for diligence. -Yes, we can drop Project ID

kevzak commented 5 months ago

Additional fields to consider removing from template:

Custom multisig Check this box off if you have explicitly been asked to by the governance team.

Not sure if custom multisigs is still a thing. Would ask Keyko and or Galen.

Identifier If needed Filecoin team will fill up this field later on. You can skip this field.

Identifier I'm not sure what that leads to.

kevzak commented 5 months ago

Data Preparation questions that are optional, but could be built to be required: