Sure. I'll keep that in mind.
On Tue, 26 May 2020 at 09:26, James Cameron <qu...@laptop.org> wrote: > Thanks, Anindya. > > Yes, you will find communication fine within your group as a > consequence of meeting regularly. That's good. > > However, not everyone is in your meeting, and nor should we expect > them to be. > > There is a risk of excluding community members by accident. It > happens often with GSoC at Sugar Labs, because students are spending > seven hours a day, mentors at least one hour a day, and everyone else > some smaller time each day. > > You can link to your GitHub Projects page in future updates; > https://github.com/meganindya/musicblocks/projects/1 > > On Tue, May 26, 2020 at 09:00:03AM +0530, Anindya Kundu wrote: > > Dear James, > > > > Thanks for the feedback. In the last meeting before the interruption I > briefly > > informed that I was exploring the feature. > > > > Walter has been walking me through some of the important code, and I'm > > experimenting to figure out how to create the required class structures. > I feel > > there will be a lot of moving parts, and so keeping a dynamic log is > crucial > > for us to synchronize along, and keeping it close to the code feels > helpful. > > > > I'll bring this up with him in today's meeting and push an update. Since > we're > > having a brief group meeting every weekday, I think communication should > be > > fine. > > > > On Tue, 26 May 2020, 2:47 am James Cameron, <[1]qu...@laptop.org> wrote: > > > > Welcome back, Anindya. > > > > I'm very familiar with electricity transmission networks. After a > > severe storm, replacement components are taken from storage and put > in > > service, and new component orders made. The delay you experienced is > > expected. > > > > Be cautious about using Projects feature. I've used it too. It is > > good for organising work, but you must take the time to measure > > engagement by others, otherwise it creates an isolation. Once the > > isolation is identified, you have to do two things each day (a) > update > > the project, and (b) tell people you updated the project. > > > > On Mon, May 25, 2020 at 06:15:41PM +0530, Anindya Kundu wrote: > > > Hello, > > > > > > Thanks for understanding my situation. Electricity has finally been > > restored > > > and things are recovering. There is an issue with the broadband > which > > will > > > hopefully be fixed in a couple of days, now that the > electricity is back. > > > > > > I joined our daily meeting today from my phone, barely getting in > before > > it > > > ended. I had a quick chat and informed about my state. I'll be > meeting > > tomorrow > > > half an hour early with Walter, before out group gathering. > > > > > > Meanwhile, I'll get back to work by tonight. I'll start with some > > experiment > > > code I was trying out, to eventually get on with the Note class > we were > > > discussing. > > > > > > I've previously mentioned that I'll be working on a branch > wip-note-class > > in > > > [1]my fork of Music Blocks. I was exploring the 'Projects' feature > on > > GitHub, > > > and found that it can be useful. I've created a project in the said > > repository > > > and I'll be updating my progress there. > > > > > > Regards. > > > > > > Anindya Kundu > > > > > > References: > > > > > > [1] [2]https://github.com/meganindya/musicblocks > > > > -- > > James Cameron > > [3]http://quozl.netrek.org/ > > > > References: > > > > [1] mailto:qu...@laptop.org > > [2] https://github.com/meganindya/musicblocks > > [3] http://quozl.netrek.org/ > > -- > James Cameron > http://quozl.netrek.org/ >
_______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel