Re: Data Portability Task Force in the SocialCG

I'd be happy to co-edit the Portability report, fwiw.

On Fri, Mar 8, 2024 at 2:35 PM Lisa Dusseault <lisa@dtinit.org> wrote:

> Oh I am a big fan of tracking issues.   I do especially like to manage
> lists of issues to help with communication and transparency because a giant
> unfiltered list of issues doesn't tell you what a team is or is not doing,
> so at some point
> * Some issues will get closed as "not doing" - a list of things you're not
> doing is so valuable to maintaining scope and ability to finish work!
> * Some things that would be nice but are overbroad or underspecified will
> be replaced with (usually several) smaller, more scoped issues
>
> That seems like normal practice in actively-managed open source and
> private software project management, but it's less normal practice in
> specification work.
>
> Lisa
>
> On Fri, Mar 8, 2024 at 7:15 AM Evan Prodromou <evan@prodromou.name> wrote:
>
>> So, I don't know if Lisa is OK with it, but I think adding issues to the
>> Git repository is a great way to ask questions and get them answered.
>>
>> https://github.com/swicg/activitypub-data-portability/issues
>>
>> Also, I authored that document for our data portability special session
>> at TPAC in Seville last year. It is very hand-wavy. It only describes
>> the current state of data portability on the Fediverse, and does not
>> suggest or promote any new methods.
>>
>> As I'm currently editing the AS2 and AP documents, and co-editing the
>> AP/Webfinger profile report, I'd like to at least get someone to co-edit
>> the data portability report, if not take it over completely. So, that's
>> probably my big question for next week!
>>
>> Evan
>>
>> On 2024-02-13 4:18 p.m., Scott wrote:
>> >
>> > This is exciting to see. I think this is a much needed feature.
>> >
>> > I do have some questions about the existing statements in the git
>> > repository and how that would work in real life. But I can save those
>> > for when it is more appropriate.
>> >
>> > Thanks for taking up the post Lisa.
>> >
>> > Scott
>> >
>> >
>> > On 2/13/2024 2:43 PM, James wrote:
>> >> Thank you for sharing this note, Evan.
>> >>
>> >> I sincerely appreciate your volunteeering to steer the group, Lisa.
>> >>
>> >> I am excited to see what the community does to advance this topic!
>> >>
>> >> James
>> >>
>> >>
>> >> On Tuesday, 13 February 2024 at 20:34, Evan Prodromou<
>> evan@prodromou.name>  wrote:
>> >>
>> >>> As mentioned previously, we decided to do a Data Portability Task
>> Force
>> >>> at TPAC last year. I'm happy to say that Lisa Dusseault has
>> volunteered
>> >>> to steer this task force forward. She has a sterling reputation in
>> >>> standards development and her current role at the Data Transfer
>> >>> Initiative adds even more relevance. Thank you Lisa!!!
>> >>>
>> >>> As of right now, there's a GitHub repository for managing
>> requirements,
>> >>> documents, and code for this task force:
>> >>>
>> >>> https://github.com/swicg/activitypub-data-portability/
>> >>>
>> >>> Probably the best way to start collecting requirements is through the
>> >>> GitHub issue tracker:
>> >>>
>> >>> https://github.com/swicg/activitypub-data-portability/issues
>> >>>
>> >>> I also moved the data portability report draft from the ActivityPub
>> repo
>> >>> to this one:
>> >>>
>> >>> https://swicg.github.io/activitypub-data-portability/
>> >>>
>> >>> If data portability is important to you, please get involved with this
>> >>> task force. Thanks!
>> >>>
>> >>> Evan
>>
>