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

best practices / software maintenance guidelines #119

Closed
kba opened this issue Jul 7, 2020 · 3 comments
Closed

best practices / software maintenance guidelines #119

kba opened this issue Jul 7, 2020 · 3 comments
Assignees

Comments

@kba
Copy link
Member

kba commented Jul 7, 2020

We had a similar document prepared for an OCR-D workshop in 2019 whose recommendations should be integrated into the best-practice document.

ht @bertsky

@bertsky
Copy link
Collaborator

bertsky commented Aug 24, 2021

These recommendations are nearly complementary to the current dev-best-practice document. I believe this is rather urgent, since in the next weeks many new collegues will commence work.

BTW, another example for coding guidelines exists in the Kitodo project. They elaborate on branching / PR rules and developer vs. reviewer roles. Also, communicating new efforts on time and updating specs is required here. Plus it makes some remarks on coding style (for Java and PHP). AFAICS we have nothing explicit for Python yet (should at least mention PEP8).

@bertsky
Copy link
Collaborator

bertsky commented Aug 25, 2021

related: #112

@kba
Copy link
Member Author

kba commented Apr 25, 2023

Let's keep discussion in #112 which is closely related.

@kba kba closed this as completed Apr 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants