Open Office - 6th April 2023

[djfnd]

Agenda

meet.google.com/uwf-pmat-xos

Lens

• Grant update
• Development update
• Planning month 1 + milestones
  • Allocation of grant discussion

ENS

• Grant update
• Discussion re: what an application may contain

Gitcoin

• "Beta" round is now open
• https://gitcoin.notion.site/gitcoin/Grantee-Onboarding-Guide-Beta-Round-c0ac6de4b9694b17b970e5d0743e5791

ELI5 documentation

• https://github.com/orgs/neume-network/discussions/5
• https://app.excalidraw.com/s/3zCU7mS2gw0/7rleTYbcwWt

Maintainers review

• Final discussion & confirmation
• https://github.com/orgs/neume-network/discussions/7

neume multi-sig

• We did not need one for the lens grant, but may need one in the future, propose that we extend github maintainers role to multi-sig sign-off
• Note, @djfnd currently holds "neume.eth", which we should transfer to the neume multi-sig

Curation

• PA: https://github.com/orgs/neume-network/discussions/8
• Indexing based on an array of wallets: https://github.com/orgs/neume-network/discussions/14

Dev

• Catalog -> Zora V3: https://github.com/orgs/neume-network/discussions/12
• Any improvement that we can make to proactively/automatically spot strapi getting blocked (e.g.: https://github.com/orgs/neume-network/discussions/11)
• Access to HIFI's strapi + transcoding service

...
Please add any other topics to the comments below and I will update this.

[estmcmxci]

Neume Sync (04.06.23)

Tl;dr

The group discussed funding-related topics, including a grant for integrating Lens. They also discussed ENS and its public goods funding rounds, and the possibility of submitting their project to consecutive rounds to increase their chances of winning. They talked about Lens and the need to create milestones for potential grants. Dan provided updates on his lens strategy and plans to write about changes to the database. They also discussed development topics such as increasing maintenance responsibilities, a new multisig, and updating Catalog and Strapi. They talked about updates to their project and plans to edit the Gitcoin funding page and draft ELI5 documentation. Kevin proposed including PA in the company's outreach efforts and submitted a proposal for funding support.

Participants:

• Dan
• Pierre
• Vaibhav
• Marcus
• Kevin

--

Summary

During the meeting, the group discusses funding-related topics, including a grant for integrating Lens. The grant is structured to support $15,000 in total, split into three payments of $5,000 each for completing milestones. They also discuss ENS and its public goods funding rounds, which have three tiers and focus on projects that benefit the entire Ethereum ecosystem. The group considers submitting their project (Neume) to consecutive ENS PG rounds. Finally, they discuss Lens, with $15,000 available split into three payments of $5,000 each. They need to create a milestone for the first month and get an update on progress from Vaibhav. The initial scope requires three milestones, but it may take up to two months to complete the main integration.

Dan believes that it will take around two more months to develop the lens strategy to the discussed stage. He has shared his plans and general strategies during a recent call and is currently working on changing the database from level db to escalate. He plans to write about this on the GitHub discussions to keep everyone informed. Dan thinks that initially, bringing in other people to work on the project would be a hindrance, but once everyone is in sync and there are protocols in place, it will be beneficial. They plan to define milestones to show progress for potential grants and may consider adding internal milestones. Additionally, Dan has access to the Lens Telegram developer group and can add Vaibhav to the group. Dan also discussed Watcher.eth's question about indexing based on an array of predetermined wallets with Riff, a company formerly known as Beats XYZ, which is interested in their project.

The chat covers various development topics, including the decision to increase maintenance responsibilities for Vaibhav and Kevin, the need for a new multisig, V3 Catalog and Strapi. There is a recurring bug with Strapi that needs monitoring, and Riff is interested in having access to Strapi transcoding. Dan is working on changing the database, which will result in a change to the schema and the need to rewrite some of the code in the Strapi pipeline. They also discuss the possibility of open sourcing the strapping transcoding piece, which will be discussed further in an upcoming meeting with the CEO. The team believes that the current integration is working and can use it if necessary.

Marcus, Vaibhav, and Dan discussed a few updates related to their project. First, Gitcoin is starting a funding round, and they have already created an initial page for it using Gitcoin builder. They plan to edit it before it goes live on April 17th and encourage as many people as possible to contribute to their project. They also discussed the ELI5 documentation, which looks good so far, but they need to consider having multiple schemas for each strategy in the future. They plan to draft the content in HackMD and decide on the final location for publishing later. Marcus will review the diagram and start writing definitions for each component, and he may need guidance from someone more familiar with the technical side. Ultimately, they want to produce high-quality content with input from the builders who are experts in the field.

During a meeting, Kevin proposed including PA (Public Assembly) in the company's development and outreach efforts. He also submitted a proposal to PA for funding support. Dan agreed with the plan and emphasized the importance of communicating Neume's projects to a wider audience and exploring grant opportunities. Kevin mentioned his plan to create a blog post about the lens piece and to include PA in it. The group discussed various matters, including milestone plans for the first month. The meeting notes will be shared with everyone.

Overview:

Development Topics:

• Increasing maintenance responsibilities for Vaibhav and Kevin
• Need for a new multisig
• Updating Catalog and Strapi
• Recurring bug with Strapi needs monitoring
• Changing the database from level db to escalate

Funding-related Topics:

• Grant for integrating lemons into a new permanent fulcrum, $15,000 split into three payments of $5,000 each
• ENS public goods funding rounds with three tiers, projects that benefit the Ethereum ecosystem
• Lens grant with $15,000 split into three payments of $5,000 each
• Defining milestones to show progress for potential grants, may add internal milestones
• Gitcoin funding round, encouraging contributions to their project

Project-related Updates:

• ELI5 documentation, multiple schemas for each strategy in the future
• Drafting content for ELI5 documentation in HackMD
• Reviewing the diagram and writing definitions for each component
• Including PA (Public Assembly) in development and outreach efforts, submitting a funding proposal to PA, and creating a blog post about the lens piece

Miscellaneous:

• Dan believes bringing in other people to work on the project would be a hindrance at first, but it will be beneficial once everyone is in sync
• Dan has access to the Lens Telegram developer group and can add Vaibhav to the group if he wishes
• The team may consider open sourcing the strapping transcoding piece

--

Discussion:

During the meeting, we need to discuss the first three items on the agenda, which are related to funding and other related questions. Yesterday, I mentioned that our friend has agreed to provide us with a grant for three months, which equates to $15,000 in total, or $5,000 per month. To get the grant started, we need to establish a first milestone. The process involves putting together the first milestone, receiving the first month's payment, providing a review of our progress at the end of the month, and then creating a second milestone that will provide us with the second month's payment.

The grant application primarily focuses on integrating lemons into our new permanent fulcrum, which the grant is structured to support as 5003 times $5,000. Each $5,000 payment corresponds to a milestone, and we receive the payment upfront and then demonstrate our progress at the end. Since Vaibhav is not present, we may need to revisit this topic later to obtain an update on the project's status.

In the meantime, I propose we discuss the first milestone and reach a verbal agreement. Afterward, I can post the discussion and finalize it. If there are any questions, we can discuss them now or revisit the topic later. Moving on to the next item, let's focus on ENS. Marcus, could you lead the discussion on this topic? It appears that they have shifted their structure to include small and big grants.

— Dan

꩜

Hi everyone, I'm Marcus and it's nice to meet you all via Google Meet. I find it more personable to be on a call than just being a disembodied voice on Discord. Let me quickly share my screen to walk you through some feedback I received from the public good steward over at ens.dow. They have been experimenting with public goods funding rounds and have now broken it up into three tiers. The small grants are awarded monthly with each winning project receiving one eath. This is meant to demonstrate proof of work and that the project is beneficial for the entire Ethereum ecosystem and web3. Once a project has been successful for a certain number of rounds, it moves to the medium round where eligible projects can earn up to 10k. Finally, there's the large grants round, which is worth around 50k.

The focus is on how the projects benefit not just a specific niche like music or NFTs, but how they can be beneficial to all users on Ethereum. The top five projects according to the public good steward are Revoke.Cash, Gas Hawk, Karma Discourse, and Web3 Scaffold. These are like a Northstar for the projects that are deserving and worthy of winning a grant.

To give you an idea, we can build a leaderboard using ENS to identify NFTs according to the smart contracts. Smart contracts can have ENS names, and this could tie in nicely. This could drive more registrations to TNS, and that could be an angle to explore.

Keep in mind that the amount of youth given out is not a lot, so we need to think about submitting this project to consecutive rounds to increase the probability of winning. The site itself allows people to vote according to their token amount, and the top votes are held by Coltrane, Lobo, FireEyes Dow, and James and Cooper.

Overall, I believe this project can benefit the entire Ethereum ecosystem, and I hope we can work together to create something meaningful.

— Marcus

꩜

Thank you for sharing your thoughts. It seems to me that when it comes to ENS, it will require a sustained effort to see any financial benefit, unless we have a significant voter allocation. Given the way their system works, we will need to win them over. That being said, I think we should share our strategy for obtaining grants in the megathread that I created, and then work from there. One thing we need to consider is whether we want to pursue non-vertical-specific grants or focus on a more general direction. However, any funding we receive could help support our work without restricting anything else.

Moving on to Lens, we have $15,000 available to us, which we can split into three payments of $5,000 each. We need to create a milestone of what we want to achieve in the first month. I suggest we get an idea from Vaibhav about their progress and what they think is achievable in the first month. Ideally, most of the money would go towards developer resources, but there may be an opportunity for additional workstreams, such as curation. The initial scope requires three distinct milestones, but in reality, it may take longer to complete the main integration, which could take up to two months. It would be helpful to get an update on where we are with Lens and what still needs to be done.

— Dan

꩜

I believe it will take around two more months of development work to shape lens to the stage we have discussed. Currently, I have been able to generalize some strategies and shared my plans during a recent call. I have also been working on changing the database from level db to escalate, but I am still in the middle of it and have made some progress. However, even SQL Lite is not perfect, so there will be some trade-offs that we will need to consider. I plan to write about this on the GitHub discussions so that everyone is on the same page. Once the database work is complete, I can move on to the third part, which is actually writing the lens strategy.

— Vaibhav

꩜

Sounds good. That sounds very good. And this maybe, is maybe a silly question. But if there were other people working alongside you on this, would that help or would that actually be more of a hindrance?

— Dan

꩜

So the way things are structured currently I think it will be a hindrance at first. But once everyone is up to speed and in sync, and we have protocols in place, how to review each other's code, then I think will benefit.

— Vaibhav

꩜

Great, that makes sense! So, based on what you're saying, it sounds like we should consider bringing in other people around the second month of our project. That's a good idea. We should probably discuss this through text rather than audio. Now that we have approval, we can start shaping up the work and defining milestones. If we want to apply for further grants, we need to show that we're making progress. We can set whatever milestones we want, even if they're just internal. By the way, I have access to the Lens Telegram developer group. It's very developer-focused, and I'm not sure if it will be useful to you, but I can add you to the group if you want. Let me know. I don't have any Lens-specific questions right now, but if I have any in the future, I'll ask you to add me to the group.

Also, I spoke with Watcher.eth, who is now the CEO of Riff (formerly known as Beats XYZ). Sweetman.eth is now the CTO there. They're building out their team quickly and are interested in our project. Watcher.eth had a question about indexing based on an array of predetermined wallets, which we can discuss in the future. I think this is a good move for them to rebrand as Lift and focus on curation. They want to surface on-chain social graphs and music energy based on those indicators. If anyone is interested in this topic, we can discuss it further during the one-hour meeting.

— Dan

꩜

I just wanted to follow up on the maintainers chat we had last week to confirm that everyone is happy with the decision to increase maintenance responsibilities for Viper and Kevin Nissen. Right now, my responsibilities are minimal - mainly just making sure the project isn't destroyed. One thing I am considering is the need for a new multisig and which names we would want on it. It's not an urgent need yet, but if other grants come in, it may become necessary to transfer the lens money into the multisig. My initial thinking was to just have the maintainers as the multisig keys, but I'm open to any other thoughts.

Moving on to dev questions, Pa noted that Catalog is moving to v3. Has anyone looked into how much of an issue that will be and how different it is from the current version? It seems that Catalog went from Door to its own vertical and has a backdoor, so we need to write a new strategy for Catalog. I haven't looked into it yet, but I'm interested in hearing other opinions.
— Dan

꩜

From my perspective, I haven't looked into it yet. HiFi prioritizes musical, but catalog updating is important as it affects the product's functionality. However, it's not urgent, and we might not get to it in the next few weeks. I'll quickly look into it, but it's possible that it may not be a quick fix. Our development should align with the funding source, and Lens' funding is the core development priority. Catalog updating can wait unless there is a specific customer need. If you can do any research, it will be appreciated.

— Pierre

Okay, my second point on Dev is about Strapi. I'm not sure if there's anything we can do to prevent it proactively or if it's just one of those things where I need to keep monitoring and let you know when it happens.

— Dan

꩜

Okay, got it. So it seems that the issue with Strapi is a recurring bug where it gets stuck at a certain block number on the website, but it's not a critical issue that needs to be addressed immediately. We can manually check it every now and then and ping you if we notice the block number is not increasing. It's difficult to automate an alert for it, but we can look into giving admin access or login credentials to some team members so they can also address the issue when needed. Does that sound about right?

— Pierre

꩜

I think this ties into the third point about Strapi transcoding. Riff would be interested in having access to it, but it's ultimately a decision for Hi Fi. However, I wanted to bring it up now and suggest that this could potentially reduce the workload for unboxing if others are also involved in it.

— Dan

꩜

To be transparent, we are planning to have a meeting next week with Joe, the CEO of HiFi, to discuss the possibility of open sourcing the strapping transcoding piece. I personally don't feel comfortable making that decision on my own as it is a bigger decision that needs to be thought about from multiple angles. While I do see the value in open sourcing it, there are many parameters that need to be considered before making a clear decision. Therefore, I cannot provide a definitive answer at this time. However, we can discuss this further in the upcoming meeting.

— Pierre

꩜

Yes and I would like to clarify that the tooling that was mentioned earlier is something that has been built to convert the output from Neume into a format that can be ingested by music OS. One way to open source it would be for HiFi to act as a service provider at that level. This is something that I would consider doing if I were at HiFi. However, this is a decision that needs to be discussed with Joe, the CEO of HiFi. The idea behind Neume is to make it accessible to anyone, but since HiFi has already built this tool, it makes sense for them to provide it. If anyone has any other points or questions related to general development topics, please feel free to bring them up.

— Dan

꩜

To clarify, I have a point to make about the development work we are doing. I am currently working on changing the database and making the strategies more generic, which will result in a change to the schema we currently have. As a consequence, we will need to rewrite some of the code in the strappy pipeline we are using. The process of ingesting from noon will remain the same, but some code will need to be modified. I just wanted to give everyone a heads up that we will need to work on this in about a month.

— Vaibhav

꩜

I understand that you feel bad about having to leave now, but I think the current integration is working, and we can use it if we don't have the bandwidth to make changes. We can always go back to the old version of Neume if necessary. So, you shouldn't feel guilty about moving forward and making improvements to interact with other parties. It's important to make the transition from version x to y as smooth as possible, but don't worry too much about it. From our perspective, worst case scenario, we'll use our own needs.

— Pierre

꩜

Great, so I have a couple more points to share. First, I wanted to mention that gitcoin is starting a big funding round. You can create your bid on your page right now, and it will go live on April 17th. I've already created an initial page for you using the gitcoin builder, but I can't share it yet because I'm using a different version of Chrome. Let me just show you what to do on my screen. Okay, so I've put together some images and a simple description that we can edit later.

Keep in mind that it costs gas to edit it because it's a cryptocurrency, but we can make changes until the 11th before we go live and start our marketing campaign. As a reminder, gitcoin uses quadratic funding, which means we want to get as many people as possible to contribute money because the amount of funding we receive depends on both the amount of money and the number of people who contribute.

Since our project is open source and interesting, I think we have a strong case for receiving a decent amount of funding from this. And the great thing about it is that it's general funding, so we can use it for things like the catalog we discussed earlier, or anything else that's non-specific to a chain.

Great, so just to summarize, I wanted to give an update on the gitcoin funding round that's starting soon. I've created an initial page for us on gitcoin builder, and we can edit it before it goes live on April 17th. It's based on quadratic funding, so we want to encourage as many people as possible to contribute to our project. The funding can go towards anything non-specific to a particular blockchain, like the catalog we were discussing earlier.

— Dan

꩜

--

Additionally, I wanted to talk about the ELI5 documentation. I've created a skeletal drawing and would love to get your input on it. I took Tim's original drawing and updated it to better reflect how things are working now. Please take a look and let me know if there's anything we can improve or clarify. The drawing is in the chat above.

— Dan

꩜

From my understanding, the documentation looks good so far. However, there are a few things that we may need to consider in the future. One thing is that each strategy may need its own database and schema. Currently, the catalog, sound, and lens are all using the same database and schema. But if we move towards a more generalized crawler, we may need to have multiple schemas since one schema may not be suitable for all platforms. These are just some thoughts for us to keep in mind as we move forward.

— Vaibhav

꩜

Marcus, we you and I started talking about the beginning. Is this useful for kind of like what you were hoping for?

— Dan

Just to clarify, have we determined where we will host the documentation? I plan on writing everything on HackMD, but I'm unsure where we will ultimately push it.

— Marcus

꩜

I agree. Let's start by drafting the content in hack MD and then we can figure out where to publish it later. As for the final location, I still think it would make sense to have a dedicated section for documentation on the website, but I'm open to other ideas as well. Ultimately, what's important is the quality of the content we produce.

— Dan

꩜

Yeah, my plan is to review the diagram and start writing definitions for each component. Then, I'll compare my definitions with the existing writing in the repository. I may need some guidance from someone more familiar with the technical side if I'm not sure I'm going in the right direction. Ultimately, the builders are the experts, so it's important to get their input.

— Marcus

Sure, let me clarify my understanding. So Kevin, you suggested that we should include PA (Public Assembly) in the developments and strategies that we're working on, and also mentioned using See as a use case. I just saw the proposal that you submitted to PA, which is linked in your comment. I think your proposal is to apply for some funding from PA to support this idea. As far as I know, you're taking the lead on the curation and indexing aspects of the project, and I think that's where this suggestion fits in. Do you have any other thoughts or ideas you'd like to add to this?

— Dan

꩜

So, to clarify, I think it's important to discuss how Neume's different projects will be communicated to the public and how we can expand our outreach efforts. This includes looking at the grant opportunities available and figuring out how to best present our projects for potential funders. We should aim to explain our work in a way that is accessible to a wider audience, especially those outside of our immediate community. It's important to remember that having more individuals involved in our projects can lead to greater success, particularly in the quadratic sense.

— Kevin

꩜

Sure, I agree with your plan. Tomorrow, I am planning to create a new blog post to announce the lens piece and discuss what's coming up in the next few months. We should definitely include public assembly in that.

I think it's great that public assembly has found a need for this tool, as I have seen it being used in other projects like Gold Sky and other indexes. It's a good time to be providing an alternative that is open source and perpendicular to the current trend of building blockchain applications in a SAS-like manner. It validates our project's original assumptions.

I think that's all I wanted to discuss. Does anyone have any other urgent matters they would like to talk about?

Thank you all for joining the call. I will create a discussion around the milestone plans for the first month and once we agree on it, we will move forward. I'll share the notes from the call. Thanks, everyone. Talk to you soon.

— Dan

tags: Neume

[djfnd]

Thanks. The summary is a bit wrong, but the long form is good to have!

[estmcmxci]

AI still needs more improvement! I’ll make sure to write some manual notes next time to improve the accuracy — could you perhaps suggest an edit to the summary to reflect this?

Here’s the write-enabled doc: https://hackmd.io/@estmcmxci/neume-sync-04-06-23

—

Otherwise just let us know here what aspect of the summary is incorrect and we can just slash it out of the discussion to ensure there’s no confusion. Thanks!

[estmcmxci]

Actually reading the summary now and see here where I can make some corrections / slashes already.. I’ll fix it up!