-
Notifications
You must be signed in to change notification settings - Fork 228
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
2019 ES-Team objectives #1182
Comments
Thanks for opening the ticket Adam. |
I'm not ignoring the pings. I only fear that I will not be able to participate much in this until the end of March. (I finish classes and leave the position of director of the academic journal of my institution). However, I would like to read proposals for the rest of the team. For now, here are the points to discuss as there were on #1179:
|
I think we should schedule a Skype meeting apart from the English team. Creo que deberíamos reunirnos por separado todos los editores, antiguos y nuevos, y hablar sobre el tema. A mí, en concreto, me interesa saber cómo nos posicionamos sobre temas políticos o geopolíticos relativos a la lengua, etc. |
Algunas tareas que podríamos discutir en esa reunión: |
Aparte de las tareas propuestas por @arojascastro , quisiera proponer los siguientes temas para la reunión.
Paralelamente a ello, me parece importante discutir:
|
Víctor, creo que a lo que te refieres con lo siguiente
Soy yo como parte del Technical Team. Por ejemplo, Matt me menciona en cualquier cosa que tenga que ver con añadir enlaces, arreglar algún archivo, etc. |
@jenniferisasi , exacto, acabo de hacer la revisión de roles y ya te vi:
Debí decir si necesitas apoyo del resto del equipo. |
Creo que podemos cerrar esto y, si queremos volver a charlar sobre el tema, convocar una reunión en el futuro y crear un ticket con la agenda como hizo Jennifer. |
Building from the discussion in #1179 @vgayolrs has suggested that the ES-team needs to discuss some strategic objectives for the project. I've opened this ticket to host those discussions as it is separate from #1179
The text was updated successfully, but these errors were encountered: