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

Additional advice for developers and designers in 'code in the open' #26

Open
ElenaFdR opened this issue Oct 28, 2020 · 1 comment
Open
Labels
enhancement New feature or request

Comments

@ElenaFdR
Copy link

ElenaFdR commented Oct 28, 2020

Is it redundant to ask developers and designers to consider eventual publication/public working in all of their project design? To plan for their work to be open even while they're still working on a closed prototype?

For example, at the COVID app development webinar, we heard that apps were developed in private (due to the highly political/sensitive nature and media scrutiny), and then had to be fully reviewed for discouraging or embarassing code documentation or commit messages before publication.

@Ainali
Copy link
Contributor

Ainali commented Oct 28, 2020

Even if it would be redundant, I think it still might be a good idea. Working radically in the open is still quite unusual, so extra reminders might be necessary for people not defaulting to a closed process/tool.

@ElenaFdR ElenaFdR added the enhancement New feature or request label Oct 29, 2020
@Ainali Ainali transferred this issue from standard-for-public-code/standard-for-public-code Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants