Pre meeting, per meeting, developer activities page It is a good idea to as part of any roll call, for each to say what they are working on, plan to, amount of time they plan to spend in development for the next month. Along with anything else they feel others should know about their activities past, present or future. That is something good for recurring, every meeting. Rather than spend time at the meeting. May have a phab page/issue or something per meeting. For each to put such down like in a table format or something.
That way each can review just prior to meeting and have insight into each other. Which may help with speeding up discussion in meeting. Either way tends to help keep everyone be on the same page, awareness of what is going on over all, etc. Also can help others outside the project know who is working on what without having to follow commits. May even make that part of some meeting template for topics, date, time, who will attend, who will not, and anything else for each meeting. -- William L. Thomson Jr.
pgp1UBNsbQFNs.pgp
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
