You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This doesn't directly concern the code of this repo but I'm creating an issue here for tracking and reference.
iD is a large project with dozens of discussions occurring in parallel both on and off GitHub. This results in an uneven understanding of the project across the community, leaving room for confusion and cynicism. There are reasoned arguments behind all the changes we make, but if users never hear them then they're left to jump to their own conclusions based on their preconceptions.
We should create a blog that answers the question "what's going on with iD?" Content could include explanations of upcoming features, highlights of new releases, event and community news, and roadmaps of where the project is headed long-term. Links to blog articles could be circulated easily in all relevant OSM channels.
On an implementation level, I suggest using GitHub Pages under the ideditor organization.
The text was updated successfully, but these errors were encountered:
This doesn't directly concern the code of this repo but I'm creating an issue here for tracking and reference.
iD is a large project with dozens of discussions occurring in parallel both on and off GitHub. This results in an uneven understanding of the project across the community, leaving room for confusion and cynicism. There are reasoned arguments behind all the changes we make, but if users never hear them then they're left to jump to their own conclusions based on their preconceptions.
We should create a blog that answers the question "what's going on with iD?" Content could include explanations of upcoming features, highlights of new releases, event and community news, and roadmaps of where the project is headed long-term. Links to blog articles could be circulated easily in all relevant OSM channels.
On an implementation level, I suggest using GitHub Pages under the ideditor organization.
The text was updated successfully, but these errors were encountered: