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

Decision Record for HfLA's Code of Conduct branch #4250

Closed
1 of 6 tasks
Tracked by #4243
jdingeman opened this issue Mar 22, 2023 · 7 comments
Closed
1 of 6 tasks
Tracked by #4243

Decision Record for HfLA's Code of Conduct branch #4250

jdingeman opened this issue Mar 22, 2023 · 7 comments
Assignees
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue feature: code of conduct Feature: Wiki role: back end/devOps Tasks for back-end developers size: 1pt Can be done in 4-6 hours

Comments

@jdingeman
Copy link
Member

jdingeman commented Mar 22, 2023

Overview

We need to have documentation of HfLA Code of Conduct being behind the master branch. For this issue, you will create a Decision Record for this so that we have transparency for our choice to keep the branch behind the master branch.

Action Items

HfLA is no longer bound by Code for America's Code of Conduct, so we are able to keep our own Code of Conduct without needing to update it to the latest CfA Code of Conduct.

  • We are currently in the process of moving the old wiki to the new website-wiki repo, so we will not be making any changes or additions to the old wiki at this time. Thus, we will be adding wiki content through a different process now. Read How to Contribute to the Wiki

Action Items to be completed when new wiki is ready

Resources/Instructions

@jdingeman jdingeman added role: back end/devOps Tasks for back-end developers Feature: Wiki Complexity: Small Take this type of issues after the successful merge of your second good first issue size: 1pt Can be done in 4-6 hours ready for product labels Mar 22, 2023
@jdingeman jdingeman added this to New Issue Approval in Project Board via automation Mar 22, 2023
@jdingeman jdingeman added this to the 08. Team workflow milestone Mar 22, 2023
@ExperimentsInHonesty

This comment was marked as outdated.

@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed Ready for Prioritization labels Mar 23, 2023
@jdingeman jdingeman added Ready for Prioritization and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Mar 24, 2023
@jdingeman

This comment was marked as outdated.

@ExperimentsInHonesty ExperimentsInHonesty moved this from New Issue Approval to Prioritized backlog in Project Board Mar 24, 2023
@vincentdang vincentdang self-assigned this Apr 7, 2023
@github-actions
Copy link

github-actions bot commented Apr 7, 2023

Hi @vincentdang, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

@vincentdang vincentdang moved this from Prioritized backlog to In progress (actively working) in Project Board Apr 7, 2023
@vincentdang
Copy link
Member

i. Availability: This Friday and weeknights next week.
ii. ETA: TBD (I still have questions haha).

@jdingeman
Copy link
Member Author

Hi @vincentdang - please see update to contributing to the wiki.

@vincentdang
Copy link
Member

vincentdang commented Apr 12, 2023

(In progress)
This is a record in the Decision Records on Solutions Adopted.

Issue

  • HfLA is no longer bound by Code for America's Code of Conduct, so we are able to keep our own Code of Conduct without needing to update it to the latest CfA Code of Conduct.

Problem Statement

  • Need a new code of conduct specific only to HFLA and separate from Code for America.

Potential Solution

A new code of conduct needs to be drafted to stand as the main source of rules and regulation for HFLA members to adhere to.

Thus, several issues were created in order to organize the development of a new Code of Conduct (coc). They were as follows: differential analysis in order to identify key changes that will distinguish HFLA’s code of conduct from COA, create a new HTML page for it, create a decision record (this), and finally to make it go live.

When finished we should follow https://github.com/hackforla/codeofconduct instead of https://github.com/codeforamerica/codeofconduct

There are still some issues (including front end) causing the coc branch to be behind the masters. See below.

Issue Summary:

  • The New Code of Conduct page is planning on having a top nav and footer.

  • There may be additional policy changes needed by June 1st, 2023.

  • A dependency between coc pages exist (.md and non- .md) and needs to be redirected.

Notes:

  • A Spanish translation may come later.

Feasibility Determination

  • The HFLA code of conduct has been implemented partially but still has issues and needs to be worked on.

@jdingeman
Copy link
Member Author

Hi @vincentdang - sorry for the delayed response. This looks good! I'll go ahead and close this issue.

Project Board automation moved this from In progress (actively working) to QA Apr 18, 2023
@HackforLABot HackforLABot moved this from QA to Done in Project Board Apr 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue feature: code of conduct Feature: Wiki role: back end/devOps Tasks for back-end developers size: 1pt Can be done in 4-6 hours
Projects
Project Board
  
Done
Development

No branches or pull requests

3 participants