2025-06-12 developer sync
This commit is contained in:
		
							parent
							
								
									7d68f6fef8
								
							
						
					
					
						commit
						2eb7b855b6
					
				
					 1 changed files with 35 additions and 0 deletions
				
			
		
							
								
								
									
										35
									
								
								meeting-notes/2025-06-12-developer-sync.md
									
										
									
									
									
										Normal file
									
								
							
							
						
						
									
										35
									
								
								meeting-notes/2025-06-12-developer-sync.md
									
										
									
									
									
										Normal file
									
								
							|  | @ -0,0 +1,35 @@ | |||
| # 2025-06-11 Fediversity developer sync | ||||
| 
 | ||||
| - @kiara has been updating the project proposal to reflect current ideas | ||||
|     - https://git.fediversity.eu/kiara/fedi-goals/src/branch/rewrite/ | ||||
|     - need to make sure all stakeholders are on board with the updated vision | ||||
|     - new slated project manager would need to know what they're signing up for | ||||
|     - we reviewed and discussed the draft | ||||
| 
 | ||||
| - @niols got the full integration test for deploying via the panel to pass | ||||
|     - https://git.fediversity.eu/Fediversity/Fediversity/pulls/361 | ||||
|     - we tinkered on reducing the number of hacks involved | ||||
|     - @fricklerhandwerk had some ideas for that, but the sketches need cleanup | ||||
|         - https://git.fediversity.eu/Fediversity/Fediversity/pulls/364 | ||||
| - @kiara and @fricklerhanderk continued editing the adjustments to the project proposal | ||||
|     - @kiara: whether/how to concentrate on external contributors (and if so, how to sensibly reflect that in a key result) | ||||
|     - @kiara: whether keeping the fediverse in even helps communicate our mission, considering fediversity could not fix the fediverse if we wanted to (given speed of adoption imo def isn't about self-hosting) | ||||
| - @fricklerhandwerk incorporated discussion results into the writeup | ||||
|     - https://git.fediversity.eu/kiara/fedi-goals/pulls/2 | ||||
|     - https://git.fediversity.eu/kiara/fedi-goals/pulls/3 | ||||
| 
 | ||||
| ## Draft success metrics for the adjusted objectives | ||||
| 
 | ||||
| - Implement a way to run online services emphasizing user autonomy and data portability | ||||
|     - Integration tests pass for | ||||
|         - Setting up a fediversity hosting environment from a declarative configuration | ||||
|         - Configuring, deploying, and migrating a set of dummy applications | ||||
|     - Code passes data protection audit | ||||
| - Disseminate our results by engaging the open-source community to further expand on work in this direction | ||||
|     - Present results on at least 3 conferences | ||||
|     - At least 5 applications compatible with Fediversity thanks to external contributions by 2027-03 | ||||
| - Exploit our work by enabling reproducible deployments of an initial set of portable applications | ||||
|     - There are 3 fediverse applications available out of the box: | ||||
|         - Mastodon | ||||
|         - PeerTube | ||||
|         - Pixelfed | ||||
		Loading…
	
	Add table
		
		Reference in a new issue