davidwboswell (Thu, 04 Feb 2021 20:13:58 GMT):
A chat channel for the Hyperledger Media and Entertainment SIG. All are welcome.

davidwboswell (Thu, 04 Feb 2021 20:13:58 GMT):
The Media and Entertainment Special Interest Group (ME-SIG) brings together technical, academic, and industry-related expertise in order to solve long-standing problems in the creation, fair distribution, and legally appropriate attribution of media assets (film, television, e-books, audiobooks, hi-res gallery or museum images, photojournalism, games, e-sports, and so forth).

DavidMacFadyen (Fri, 05 Feb 2021 00:47:13 GMT):
Has joined the channel.

DavidMacFadyen (Fri, 05 Feb 2021 00:47:14 GMT):
Hi to all - David MacFadyen here welcoming all interested parties to the Special Interest Group for Media and Entertainment! :musical_score: :cinema: :performing_arts: :paintbrush: :newspaper: :hyperledger:

sergiorojas (Fri, 05 Feb 2021 15:49:29 GMT):
Has joined the channel.

sergiorojas (Fri, 05 Feb 2021 15:49:29 GMT):
Hello

davidwboswell (Fri, 05 Feb 2021 16:00:08 GMT):
Hi @sergiorojas -- hope you're doing well

roseallenm (Fri, 05 Feb 2021 16:59:54 GMT):
Has joined the channel.

VipinB (Sat, 06 Feb 2021 11:24:43 GMT):
Has joined the channel.

VipinB (Sat, 06 Feb 2021 11:24:43 GMT):
hey how about :writing_hand:

VipinB (Sat, 06 Feb 2021 11:25:50 GMT):
Poetry to the moon

DavidMacFadyen (Sat, 06 Feb 2021 18:13:39 GMT):
:question:

alexchainstack (Mon, 08 Feb 2021 02:21:45 GMT):
Has joined the channel.

alexchainstack (Mon, 08 Feb 2021 02:21:45 GMT):
Hi everyone! Thank you for setting this up, David.

alexchainstack (Mon, 08 Feb 2021 03:12:19 GMT):
I was checking the group's wiki page to get to know you all a bit more through the members' directory: https://wiki.hyperledger.org/display/MESIG/Media+and+Entertainment+SIG

alexchainstack (Mon, 08 Feb 2021 03:13:40 GMT):
It looks like the link to the members list leads to the Climate Action SIG, though. Happy to fix it if you can share the location of the directory.

Brettsy (Mon, 08 Feb 2021 13:06:58 GMT):
Has joined the channel.

Brettsy (Mon, 08 Feb 2021 13:45:49 GMT):
Morning all @davidwboswell attempting to add myself to the Member Directory returns Not Permitted Im logged in to LF as brettr@accurati.us - any assistance would be great - no rush for this Thank you https://wiki.hyperledger.org/display/MESIG/Member+Directory

davidwboswell (Mon, 08 Feb 2021 15:39:32 GMT):
@alexchainstack -- thanks for pointing out that there is a link that points to the Climate Action SIG. i used some of their wiki pages as a template so i may have missed updating a link somewhere. feel free to edit the wiki to fix or let me know where you're seeing that link and i can update it.

davidwboswell (Mon, 08 Feb 2021 15:42:20 GMT):
@Brettsy -- sorry to hear that you're running into an issue editing the wiki. i double checked the permissions on the wiki and it seems like everyone should have access, but maybe there is something going on with your account. could you try logging in again and trying to edit the member directory page? and could you try editing a different page on the wiki too -- we could see if there is something specific about that one page or if this is a general issue.

Brettsy (Mon, 08 Feb 2021 17:18:44 GMT):
Thank you...will do and will advise

Brettsy (Tue, 09 Feb 2021 12:42:01 GMT):
Morning David @davidwboswell I have no problem logging in/out of my LF account (brettr@accurati.us) Did that. When I attempt to log in to my account from the wiki page (https://wiki.hyperledger.org/display/MESIG/Meetings) I get the NOT PERMITTED page - to be clear, I can access the MESIG wiki if Im NOT logged in. Once I log in, the page only shows the NOT PERMITTED. I can see the toolbar but I can no longer see thePAGE TREE or content. Thanks for your help. No rush here. I should make you aware that I have two LF accounts but I use different emails for each. brettr@bigbtc.ca and brettr@accurati.us - On my brettr@accurati.us LF account I added an alterante email brettr@bigbtc.ca. FYI I maintain the the bigbtc profile because Im registered for CHFA + CHSA exams and do the HL Southern Georgian Bay MEETUP under that address. Sorry if the duplicate accounts is messing you up.

Brettsy (Tue, 09 Feb 2021 12:43:30 GMT):

not permitted.PNG

gskerry (Tue, 09 Feb 2021 16:26:32 GMT):
Has joined the channel.

gskerry (Tue, 09 Feb 2021 16:26:32 GMT):
Same error for me. Can view when not logged in, but as soon as I log in with LFID, get the same screen

gskerry (Tue, 09 Feb 2021 16:27:54 GMT):
Emailed helpdesk@linuxfoundation.org but got a bounceback that it doesn't exist. :neutral_face:

coveloper (Tue, 09 Feb 2021 18:01:37 GMT):
Has joined the channel.

coveloper (Tue, 09 Feb 2021 18:01:38 GMT):
thanks for setting up the meeting today, great to meet everyone!

sposth (Tue, 09 Feb 2021 18:20:38 GMT):
Has joined the channel.

sposth (Tue, 09 Feb 2021 18:20:38 GMT):
Thanks for the good meeting, today on Tuesday. One comment regarding the communication channel: Slack has this great advantage that it is a tool which is broadly used by many people, who are used to dealing with multiple Slack accounts, to browsing through the messages and replying fast and in a timely manner. I personally have Slack open all the time and experience that people I work with are pretty responsive. Furthermore, you can connect e.g. Google Docs or presentation to share some notes.

davidwboswell (Tue, 09 Feb 2021 22:12:55 GMT):
@sposth -- you're right that slack is a great tool and more people prefer it to the rocket.chat option. the one bonus for using this channel though is that you are able to be in touch with other community members. for instance, if you have a question about fabric, for instance, the fabric developers are here and you can ask them questions or invite them to this channel. if the group moved somewhere else you would then be isolated from the wider community.

davidwboswell (Tue, 09 Feb 2021 22:13:20 GMT):
that having been said, the group can change if you want. just sharing my thoughts on the trade-off :)

davidwboswell (Tue, 09 Feb 2021 22:33:02 GMT):
ok, sounds frustrating. we filed a ticket with IT. something seems busted on confluence.

DavidMacFadyen (Wed, 10 Feb 2021 00:22:42 GMT):
If people would rather be on Slack, let’ me know. It’s what I use to teach with. Sorry about the dog barking today. She is usually 100% silent. :dog: :x: (Slack is arguably already a old man’s tool - a lot of my students have jumped ship in favor of Discord :))

davidwboswell (Wed, 10 Feb 2021 00:30:37 GMT):
@Brettsy and @gskerry -- can you try again? i think the issue may be fixed. IT found an LDAP bug that may have been the problem. let me know if it does or doesn't work for you.

alexchainstack (Wed, 10 Feb 2021 05:32:44 GMT):
Thank you, David. I have now fixed it - I couldn't find the link to this document https://wiki.hyperledger.org/display/MESIG/Member+Directory

alexchainstack (Wed, 10 Feb 2021 05:33:33 GMT):
Now that it's been shared here, I used it to edit the link to it on the MESIG. and add my details to the directory.

David_MacFadyen (Wed, 10 Feb 2021 18:48:54 GMT):
Has joined the channel.

David_MacFadyen (Wed, 10 Feb 2021 18:48:54 GMT):
I mention in my project proposal that my data set was donated to a muem

David_MacFadyen (Wed, 10 Feb 2021 18:48:54 GMT):
I mention in my project proposal that my data set was donated to a museum in LA. They just launched a very cool walkthrough. It should help to make the project less abstract — and also help us imagine how music could be used in this test environment as we build two platforms: heritage / museum and contemporary/ commercial https://wendemuseum.us12.list-manage.com/track/click?u=e5dde27cccb6b86e8fc849d5d&id=ac1141cced&e=9fb8316a40

davidwboswell (Wed, 10 Feb 2021 21:13:04 GMT):
that is pretty cool. fun way to check out the museum. i like the pink lenin in the entryway :)

sposth (Wed, 10 Feb 2021 21:21:50 GMT):
Very well done! It is high resolution version of https://decentraland.org/ or cryptovoxels.com/. Both platforms have attracted virtual galleries like https://superrare.co/ or https://opensea.io/. In these VR galleries the artworks are NFTs that are either for sale or just hanging on the walls for exhibition purposes. Just in a real VR :)

Brettsy (Wed, 10 Feb 2021 21:33:40 GMT):
Hi @davidwboswell Thanks for the assistance here. I logged out, cleared all LF and LF SSO cookies still same. I can log into my LF account no problems and then navigate to the wiki. I now see its ANY WIKI - not just the M/E SIG https://wiki.hyperledger.org/ that will produce NOT PERMITTED.

Brettsy (Wed, 10 Feb 2021 21:52:11 GMT):
Very cool @David_MacFadyen

davidwboswell (Wed, 10 Feb 2021 22:15:37 GMT):
@Brettsy -- ok, sounds like things are still messed up. Would you mind sending me an email with what you're seeing to dboswell@linuxfoundation.org and I'll then CC the person on the team who is in charge of wiki issues to get his opinion?

sposth (Thu, 11 Feb 2021 15:02:38 GMT):
I have questions regarding the chain governance and set-up of the distributed curation platform (DCP) on Hyperledger Fabric. 1) I assume that a blockchain using Hyperledger Fabric is permissioned in the sense that only known actors or entities can send transactions or write on the chain. Is this correct? And if so, does this apply to both networks, the MN (Museum Network) as well as the CN (Commercial Network). 2) Will the blockchain be public pnermissioned in the sense that the blockchain is open for anyone to read specific input data from the chain? Would / could there be a difference depending on the network, the MN (Museum Network) or the CN (Commercial Network). My thinking is: If you want to support trade or commercial activities, you need to provide metadata, identifiers, links to further terms and conditions which would imo require the blockchain to be open for reading purposes.

sposth (Thu, 11 Feb 2021 15:02:38 GMT):
I have questions regarding the chain 'governance' and set-up of the distributed curation platform (DCP) on Hyperledger Fabric. 1) I assume that a blockchain using Hyperledger Fabric is permissioned in the sense that only known actors or entities can send transactions or write on the chain. Is this correct? And if so, does this apply to both networks, the MN (Museum Network) as well as the CN (Commercial Network). 2) Will the blockchain be public in the sense that the blockchain is open for anyone to read specific input data from the chain? Would / could there be a difference depending on the network, the MN (Museum Network) or the CN (Commercial Network). My thinking is: If you want to support trade or commercial activities, you need to provide metadata, identifiers, links to further terms and conditions which would imo require the blockchain to be open for reading purposes.

sposth (Thu, 11 Feb 2021 15:02:38 GMT):
I have questions regarding the model, chain 'governance' or set-up of the distributed curation platform (DCP), which will be based on Hyperledger Fabric. https://wiki.hyperledger.org/display/HYP/Media+and+Entertainment+SIG+Proposal 1) I assume that a blockchain network using Hyperledger Fabric is permissioned in the sense that only known, identifiable actors or entities can send transactions or write on the chain. Is this correct? And if so, does this apply to both networks of the project: the MN (Museum Network) as well as the CN (Commercial Network)? 2) Will the blockchain be public in the sense that the blockchain is open for anyone to read specific input data from the chain? There could be a difference depending on the network, the MN (Museum Network) or the CN (Commercial Network). My thinking is: If you want to support trade or commercial activities by using blockchain technology, rightsholders need to be able to either provide metadata, identifiers, links to further terms & conditions or connect them to identifiers, identities or transactions, which would require the blockchain to be open for reading purposes. Discoverability is the most crucial advantage of trade in web 3.0 media environments to the current situation. Also think of the NFT model, where the terms are public, so that any gallery can offer, sell or resell the NFTs without the need to ask the rightsholder. If you deal with value transfer, tokenisation, ownership, transfer, decentralised identities and the like, these assets, statui, access ot keys or tokens needs to be verifiable, which would also require an open and public network, which very well can (some might say) must be permissioned. I am not sure whether Hyperledger Fabric (and/or your idea of the project) supports this.

sposth (Thu, 11 Feb 2021 15:02:38 GMT):
I have questions regarding the model, chain 'governance' or set-up of the distributed curation platform (DCP), which will be based on Hyperledger Fabric. https://wiki.hyperledger.org/pages/viewpage.action?pageId=41591166 1) I assume that a blockchain network using Hyperledger Fabric is permissioned in the sense that only known, identifiable actors or entities can send transactions or write on the chain. Is this correct? And if so, does this apply to both networks of the project: the MN (Museum Network) as well as the CN (Commercial Network)? 2) Will the blockchain be public in the sense that the blockchain is open for anyone to read specific input data from the chain? There could be a difference depending on the network, the MN (Museum Network) or the CN (Commercial Network). My thinking is: If you want to support trade or commercial activities by using blockchain technology, rightsholders need to be able to either provide metadata, identifiers, links to further terms & conditions or connect them to identifiers, identities or transactions, which would require the blockchain to be open for reading purposes. Discoverability is the most crucial advantage of trade in web 3.0 media environments to the current situation. Also think of the NFT model, where the terms are public, so that any gallery can offer, sell or resell the NFTs without the need to ask the rightsholder. If you deal with value transfer, tokenisation, ownership, transfer, decentralised identities and the like, these assets, statui, access ot keys or tokens needs to be verifiable, which would also require an open and public network, which very well can (some might say) must be permissioned. I am not sure whether Hyperledger Fabric (and/or your idea of the project) supports this.

Brettsy (Thu, 11 Feb 2021 15:48:58 GMT):
Will do, thank you @davidwboswell

davidwboswell (Thu, 11 Feb 2021 16:57:47 GMT):
@gskerry -- we think we've fixed the wiki access issue. let me know if you can't view or edit any of the wiki pages.

davidwboswell (Thu, 11 Feb 2021 16:58:52 GMT):
@sposth -- that is a good question about governance. you may also want to ask that on the mailing list. the chat channel is newer and not everyone from the list has moved over here, so you could get more people seeing and responding to your question there if you don't get a response here.

sposth (Thu, 11 Feb 2021 21:14:17 GMT):
I sent my question as email. Since this would be my first email on this list server, could you please check whether I did it correctly and the email reached the right group :)

davidwboswell (Thu, 11 Feb 2021 21:16:24 GMT):
@sposth -- yes, i see your email in the group's mailing list archives at: https://lists.hyperledger.org/g/media-entertainment-sig/topic/hyperledger_fabric_as/80568772?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,80568772

bestape (Fri, 12 Feb 2021 00:38:01 GMT):
Has joined the channel.

DavidMacFadyen (Fri, 12 Feb 2021 02:24:25 GMT):
@sposth - yup, it reached me :)

sposth (Fri, 12 Feb 2021 14:55:12 GMT):
I suggested some edits to the project wiki: https://wiki.hyperledger.org/pages/viewpage.action?pageId=41591166 1) I added to point 6. 2) I made slight edits in the format of the headings.

DavidMacFadyen (Fri, 12 Feb 2021 19:37:35 GMT):
I am posting my email here, too. One of my Inboxes thought the Russian email herein looked a bit “spammy” :)

DavidMacFadyen (Fri, 12 Feb 2021 19:37:35 GMT):
I am posting my email here, too. One of my Inboxes thought the Russian URL herein looked a bit “spammy” :)

DavidMacFadyen (Fri, 12 Feb 2021 19:37:57 GMT):
Thanks very much, Vipin and Sebastian: Let’s consider two our proposed scenarios—a Museum Network (MN) and a Commercial Network (CN). MN Our test-case participant is singular—the Wende Museum of the Cold War in Los Angeles 1. Here’s an overview https://laacollective.org/work/cold-war-spaces-at-the-wende-museum 2. and a 3D walkthrough of the building https://my.matterport.com/show/?m=6H92bxJF48K. I have donated my collection to them, but am taking archival responsibility for it. The museum’s goal is to display the collection while minimizing the likelihood of theft. Perhaps even loan out items (as suggested below). Indeed, if we draw a parallel with the application of blockchain to hi-resolution images in fine art museums and galleries, then it’s possible to imagine a scenario in which an entirely “audible” institution like the Grammy Museum in LA (https://grammymuseum.org/) could lend out metadata-rich files to lesser organizations, while monitoring their usage. The monitoring/resulting data would both help the museum plan more appealing exhibitions in the future and, in the case of living authors, get funds to those same authors in realtime. Hence my desire to include an audio player that tracks streams, as a form of file access or “usage.” The network in this case would be governed by the museum itself. The museum might want to host the collection on their own servers, or I could arrange a server setup with AWS or some similar cloud-based enterprise. In the MN instance, the logical limits of a public-facing write would be crowdsourcing of historical data, with rare tracks enriched by members of the public who know the attribution of old songs. I’ve seen this work attempted by companies such as Melodiya, which used to be the primary state recording company in the Soviet Union. Their Moscow archives are a treasure trove of badly documented tapes, wax discs, acetates, cylinders, etc—often with penciled box-notes that faded in the sunlight decades ago. Melodiya started posting snippets online to see if people knew what on earth was in all those demos... https://melody.su/en/ ———— CN Here we could split the network again into two. Let’s imagine two versions of CN: CN1. A network run by major labels CN2. A network run by minor labels—or by some regional (perhaps stylistic) team of kindred musicians. One town, one county, or one genre. In the case of CN1 we see the type of situation that makes HLF so popular with corporations. CN1 would be for a small number of participating companies with already established artists. They collectively oversee the network, storing the files in a jointly operated cloud repo. From here files would be streamed (monitoring plays simultaneously and paying out to artists directly in real time). So, while this would mean a reduction in percentage payments/cuts for the big labels, those companies would actually gain greater (and new) income from monitoring people/radio stations/shopping malls accessing the same files, 24/7. Artists are therefore paid more fairly by their labels—and labels are paid more fairly by the public. No real need for a public-facing write API here, unless one wishes to let the artists update existing information. * In the case of CN2, a more decentralized scenario transpires. No major labels—if any at all—and the artists together host their data. Here the public-facing read/write functionality is essential, since the artists record and catalog everything themselves. If, therefore, we imagine a CN2 in which non-members are invited to join a regional or stylistically specific network, then everything would be added to that network by potential strangers. (Or by recently accepted members.) The advantage here for CN2 is that rotation figures on Spotify are, for most artists, risible. I am not sure what happened to the project Forgotify (https://routenote.com/blog/forgotify-brings-the-unheard-music-of-spotify-to-your-ears/) but it’s currently down; it usually hosts countless tracks that have (almost) never been played on Spotify and then randomizes playlists from them. Most tracks are either never played or immediately forgotten. A local scene (“music from Pittsburgh”) or one style (“Estonian folk music”) could gather more attention and income if it broke away from the bottomless ocean of Spotify, Apple Music, etc and promoted itself to less numerous but more committed fans, claiming all income in the process. D

sposth (Sat, 13 Feb 2021 12:44:43 GMT):
# Re/ MN For the MN I see two use cases: 1) Digital lending 2) Decentralised curation and records management Re/ 1) Digital lending The rightsholder (Wende Museum) could generate and register ISCC, and then associate metadata and licensing terms to the ISCC on the blockchain. The assets can be tokenized as fungible or non-fungible tokens. A third party curator and possible licensee could select an individual choice of content from the rightsholder collection that he wants to use for his purpose. If this purpose has been granted by the licensor as part of the licensing terms associate to the ISCC, a licensing transaction can be triggered in various ways: a) The licensee could acquire a defined number of streams. In this case the number of streams / loans could be tracked by a media player or otherwise defined. b) The licensee could acquire a right to stream for a defined period of time. Access to the content could be granted by an application that checks verifiable credentials (VC) which have been issued by the rightsholder and licensor to the licensee after the licensing transaction. c) Content could be provided for research purposes according to the general academic standards. If those models would work, this could be a valuable proof-of-concept for the entire industry and would benefit media organisations in all parts of the world. Tracking of digital lending is an issue for publishers in all parts of the world. Re/ 2) Decentralised curation and records management The rightsholder (Wende Museum) could generate, register ISCC and associate metadata with the ISCC. a) Third party archives and museums could do the same and identify same or similar digital assets. b) In case of matches, metadata could be exchanged, suggested, enriched, added, verified or corrected for quality ensurance (crowdsorcing of historic data) by verified parties. # Re/ CN A comment on the CN distinction. A closed, proprietary service with a joint fulfillment and distribution service might be hard to establish. From my conversations with the music industry and long-time collaboration with a major audio distributor, this represents the current status quo. There is not a lot of revenue to add or convenience to gain by switching an existing business to a different service that matches with the current situation. However, I see use cases that are of interest: - Easier access to and exchange of better metadata – this is the golden standard of problems. - Compensation of composers of audio works – obviously a big problem in the music industry. - Supporting microsales for sync licenses for social sharing – how can users legitimately license and share a lady gaga on their social media? Supporting tokenization (NFTs) for audio. - Supporting competition in the subscription market – How could I open up a subscription service for my customers and audience and easily get access to the licenses? (compare it to college radio stations), or think of legal, licensed music streaming in the Metaverse (Decentraland, Cryptovoxels), on Discord, on Clubhouse, Zoom, etc. In my opinion, these use cases could – in principle – be set-up with the same technology and processes as the MN, so that structurally, eventually MN and CN might not be all too different in the basic requirements, but the use cases might be different. Especially in the expression of rights (rights expression languages REL) and the fulfillment (DRM, access control) post-transaction. Best, Sebastian

DavidMacFadyen (Sun, 14 Feb 2021 22:47:35 GMT):
Happy Valentine’s Day to one and all! :rose: :cupid: I have rearranged, re-edited, and simplified the project statement, increasing readability and proposing that we do everything possible to hide diverging transactions (for-profit, non-profit) behind one UI. That makes life simpler for everybody. https://wiki.hyperledger.org/pages/viewpage.action?pageId=41591166 We’re getting close to a small number of project sections, each associated with a specific technology. Now’ s the time to have your say! I have incorporated Sebastian’s thoughts and notes, but wonder if he’d like to suggest how much of the section “DECENTRALIZED CONTENT IDENTIFICATION. ASSOCIATION OF METADATA AND RIGHTS MANAGEMENT INFORMATION” he’d like to replace with this section from his last email? The rightsholder (Wende Museum) could generate and register ISCC, and then associate metadata and licensing terms to the ISCC on the blockchain. The assets can be tokenized as fungible or non-fungible tokens. A third party curator and possible licensee could select an individual choice of content from the rightsholder collection that he wants to use for his purpose. If this purpose has been granted by the licensor as part of the licensing terms associate to the ISCC, a licensing transaction can be triggered in various ways: a) The licensee could acquire a defined number of streams. In this case the number of streams / loans could be tracked by a media player or otherwise defined. b) The licensee could acquire a right to stream for a defined period of time. Access to the content could be granted by an application that checks verifiable credentials (VC) which have been issued by the rightsholder and licensor to the licensee after the licensing transaction. c) Content could be provided for research purposes according to the general academic standards. I see that people are slowly moving to the Rocket Chat at HL (https://chat.hyperledger.org/channel/media-entertainment-sig) Thus far, I am not sensing any real enthusiasm for moving to Slack. Let me know if that’s not the case. The benefit of some chat-space is that the emails will lessen :)

malikhan (Wed, 10 Mar 2021 06:11:46 GMT):
Has joined the channel.

malikhan (Wed, 10 Mar 2021 06:20:25 GMT):
@sposth I had similar questions. It would be great to explore this more.

malikhan (Wed, 10 Mar 2021 06:24:44 GMT):
Hi all :wave: . Looking forward to contributing to the discussion.

malikhan (Wed, 10 Mar 2021 06:45:10 GMT):
Looks like there was a meeting today that I missed. Hopefully, I'll be all caught up by the next meeting.

davidwboswell (Wed, 10 Mar 2021 15:54:42 GMT):
@malikhan -- thanks for joining this channel and i'm glad to hear you're interested in the group. if you're interested in yesterday's call, we have a recording posted. it was a good conversation focused on NFTs. https://wiki.hyperledger.org/display/MESIG/2021-03-09+MESIG+Call

davidwboswell (Wed, 10 Mar 2021 15:55:07 GMT):
if you subscribe to the group's mailing list you'll get notifications about other upcoming calls. https://lists.hyperledger.org/g/media-entertainment-sig

malikhan (Wed, 10 Mar 2021 20:52:11 GMT):
Thank you for the video link. I have already subscribed to the mailing list.

malikhan (Fri, 12 Mar 2021 02:02:48 GMT):
I am involved in a couple of NFT projects that fall under the mandate of this group. Would it be all right to present them to the group once they are solidified? It would probably take a few months before they are ready for public eyes. However, I want to be respectful of conflict of interest and self promotion issues. My primary intention here is to collaboratively solve pressing asset management problems through blockchain technology.

davidwboswell (Fri, 12 Mar 2021 15:23:14 GMT):
@malikhan -- yes, you'd be welcome to present when you're ready to. the group already has a couple of presentations lined up and we welcome others to present as well. just email the list with details about what you'd like to present and we can schedule a time then. for reference, presentations are at https://wiki.hyperledger.org/display/MESIG/Presentations

malikhan (Thu, 08 Apr 2021 07:04:04 GMT):
Hey, haven't seen much activity here. I guess it's because more members are signed up for the mailing list. But just wanted to check if there is another communication channel I am unaware of :)

davidwboswell (Fri, 09 Apr 2021 23:49:30 GMT):
@malikhan -- yes, more people are on the group's mailing list than here. feel free to post there with any thoughts, comments or suggestions.

sposth (Tue, 13 Apr 2021 19:01:06 GMT):
Hi There, when is the next meeting? I cannot find any information, here: https://wiki.hyperledger.org/display/MESIG/Meetings

davidwboswell (Tue, 20 Apr 2021 18:01:59 GMT):
@sposth -- the MESIG calendar is at: https://lists.hyperledger.org/g/media-entertainment-sig/calendar

davidwboswell (Tue, 20 Apr 2021 18:02:14 GMT):
you can add the upcoming calls to your calendar if you'd like with the ics file there.

kenty (Thu, 29 Apr 2021 07:37:33 GMT):
Has joined the channel.

Daniela_Barbosa (Tue, 03 Aug 2021 22:27:28 GMT):
Has joined the channel.

Crispin-Sharkaroo (Mon, 23 Aug 2021 19:28:48 GMT):
Has joined the channel.

nikusingh (Mon, 17 Jan 2022 06:28:27 GMT):
Has joined the channel.

nikusingh (Mon, 17 Jan 2022 06:31:35 GMT):
Hey everyone, I am Niku Singh. Sophomore from India. I am currently learning blockchain. This sig got my interest and I would like to be a part of this sig. Just wanted to know what are the projects going on and how can i become part of any such?

Brettsy (Mon, 14 Feb 2022 14:31:28 GMT):
Hi @nikusingh - Im sorry for the long delay in replying - please visit https://wiki.hyperledger.org/display/MESIG/Media+and+Entertainment+SIG and get yourself setup and add you name to the Member Directory. https://wiki.hyperledger.org/display/MESIG/Member+Directory Look forward to seeing you there.

rjones (Wed, 09 Mar 2022 03:04:19 GMT):

rjones (Wed, 23 Mar 2022 17:26:57 GMT):