Skip to content
This repository has been archived by the owner on Sep 12, 2022. It is now read-only.

re-close this issue tracker #165

Closed
lwinfree opened this issue Apr 21, 2021 · 2 comments
Closed

re-close this issue tracker #165

lwinfree opened this issue Apr 21, 2021 · 2 comments
Assignees
@lwinfree

Comments

@lwinfree
Copy link
Member

We should re-close this issue tracker once we have finished the last website fixes. I'm opening this now to remind us later :-)
@lwinfree lwinfree self-assigned this Apr 21, 2021
@roll
Copy link
Member

roll commented Apr 29, 2021

Or might keep it open for some time till we get to some 1 issue tracker system. I think when it was close it wasn't perfect either

@roll
Copy link
Member

roll commented May 24, 2021

Agreed with @lwinfree that it will be more manageable for us if we keep this tracker (I think it was the last active repo without an active issue tracker that was creating confusion)

@roll roll closed this as completed May 24, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@lwinfree lwinfree

Labels
None yet
Projects
Open Knowledge
Archived in project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@roll @lwinfree