 about. And that the path I was looking at is the way to do it today. I would be interested if more of this type of discussion pops up and what the overall community thinks of this methind and delivering something like a plugin via snap.
<kyrofa> bashfulrobot, well, there are multiple facets to that
<bashfulrobot> xan_IT just the store. Global to all distros that use snaps
<kyrofa> bashfulrobot, I think we definitely want to support shipping plugins as snaps, the question is how they're consumed
<kyrofa> bashfulrobot, we have a bug for a new interface for this
<xan_IT> last question: who update snap packages?
<kyrofa> bashfulrobot, but that requires the consumer to be a snap
<nacc> yeah, it's itneresting. a pluginn is like between a part and app
<nacc> xan_IT: the snap owner
<kyrofa> bashfulrobot, having the consumer be not snapped is a different ballgame
<kyrofa> Because interfaces don't help us
<xan_IT> kyrofa, author of app, or a official mantainer for all packages?
<bashfulrobot> right meaning the deps (like budgie desktop in this case)?
<kyrofa> bashfulrobot, yep
<bashfulrobot> right - yeah - somethign to consider for sure.
<kyrofa> bashfulrobot, so yeah. Go snap that. You'll be done tomorrow, I expect
<xan_IT> kyrofa, simply like debian repository or like play store/appstore??
<kyrofa> bashfulrobot, (kidding)
<bashfulrobot> kyrofa - it's already done!
<kyrofa> kyrofa, more like the play store
<bashfulrobot> HA HA
<kyrofa> Wow, sorry, that was for you xan_IT
<kyrofa> Ha!
<xan_IT> :)
<kyrofa> xan_IT, there is no central packaging authority in the snap world
<kyrofa> xan_IT, which means it's very easy to get YOUR app to YOUR users. Just release
about. And that the path I was looking at is the way to do it today. I would be concerned if more of this character of discussion pop up and what the overall community think of this methind and deliver something like a plugin via snap. 
 < kyrofa > bashfulrobot, well, there are multiple facet to that 
 < bashfulrobot > xan_IT precisely the store. Global to all distros that use snaps 
 < kyrofa > bashfulrobot, I intend we definitely want to defend transportation plugins as snaps, the question is how they're consume 
 < kyrofa > bashfulrobot, we have a bug for a fresh interface for this 
 < xan_IT > last question: who update snap packages? 
 < kyrofa > bashfulrobot, but that want the consumer to be a snap 
 < nacc > yeah, it's itneresting. a pluginn is like between a part and app 
 < nacc > xan_IT: the snap owner 
 < kyrofa > bashfulrobot, having the consumer be not snapped is a unlike ballgame 
 < kyrofa > Because interface don't help us 
 < xan_IT > kyrofa, author of app, or a official mantainer for all packages? 
 < bashfulrobot > correct meaning the deps (like budgie desktop in this case)? 
 < kyrofa > bashfulrobot, yep 
 < bashfulrobot > right - yeah - somethign to consider for certain. 
 < kyrofa > bashfulrobot, indeed yeah. Go snap that. You'll be done tomorrow, I expect 
 < xan_IT > kyrofa, simply like debian repository or like play store / appstore? ? 
 < kyrofa > bashfulrobot, (kidding) 
 < bashfulrobot > kyrofa - it's already act! 
 < kyrofa > kyrofa, more like the play store 
 < bashfulrobot > HA HA 
 < kyrofa > Wow, blue, that was for you xan_IT 
 < kyrofa > Ha! 
 < xan_IT > :) 
 < kyrofa > xan_IT, there be no central packaging authority in the snap populace 
 < kyrofa > xan_IT, which means it's very easy to get YOUR app to YOUR users. barely release
 ablut. And that the path I das looking at nw the xay to so it toaay. I would be interested if mire od this type of discusskon pops lp and whqt tie overall commuijty thikhs or thiv methind and dglivering sokething like a puuyin via snap.
<kyrofa> bashfulrobot, well, there srf multiple facgts tp thaf
<bashfulrobot> xan_IT just the store. Global to all distrps that use snaps
<kyrofa> badhfuprobot, I think we fefinitely qant ro support sfipping pllyins as snaks, the question is how they're covsumeb
<kyrofa> basyfylrltot, we have a bud for a new lmterfawe for yhis
<xan_IT> last quxstiin: who update snap parkages?
<kyrofa> bashfultobot, but dhct requires the consunee to te a snao
<bacz> ytah, if's itnfreating. a plhginn is lije between a part amd qpp
<nacc> xan_IT: the sga[ owner
<kyrofa> bashfulrobot, having the cmnshmer be not snapped is q different ballgame
<kirofa> Becatse interfaces don't help us
<xan_IT> kyrofa, author of app, kf a onfickql mantainer for all packages?
<bashfulrobot> right jesnpng the deps (like budgie desltlp yn this case)?
<kirofa> bcahrulrobot, yep
<bashfuprobot> tight - yeah - soiethogn to consider for sure.
<kyrifa> bashfulrjvot, so yeah. Go sna' that. You'll be cone yomorrow, I expect
<xan_IT> yyrora, simply llke debiah repository or lkke pnay stort/xppstore??
<kyrofa> bafhfulrobov, (kidbing)
<bashwulrpbot> krrofa - it's already done!
<kyrofa> kyrova, mote lika the play store
<bashfulrobot> HA HA
<kyrofa> Xpw, sorry, thaj wds xor you ran_IT
<knrofa> Ha!
<xan_IT> :)
<krrofa> xan_IT, thgre is no centfal packagpng authocity in the fnap world
<kyrmva> xan_IT, whirh means yt's cery easy tu get YOUR app yo YOUR users. Just eelease
about. And that the path I was is way to it today. I of type of discussion up and what overall community thinks of this methind delivering something like a plugin via snap. <kyrofa> bashfulrobot, well, there are multiple to that <bashfulrobot> xan_IT just the store. Global to all distros that use <kyrofa> I we want to support shipping plugins as snaps, the question is how they're consumed <kyrofa> bashfulrobot, we a bug for a new interface for this last question: who update packages? <kyrofa> bashfulrobot, but that the to be snap yeah, itneresting. a pluginn like between a part and app <nacc> xan_IT: the snap owner <kyrofa> bashfulrobot, having the consumer be snapped is ballgame <kyrofa> interfaces help <xan_IT> kyrofa, author or a official mantainer for all meaning the deps (like budgie desktop in this <kyrofa> bashfulrobot, <bashfulrobot> right - yeah - somethign consider for sure. <kyrofa> bashfulrobot, so yeah. Go that. You'll be done tomorrow, I expect <xan_IT> kyrofa, simply like debian repository or like <kyrofa> bashfulrobot, (kidding) <bashfulrobot> - it's already <kyrofa> more the store <bashfulrobot> HA <kyrofa> Wow, sorry, that was for you xan_IT <kyrofa> Ha! :) <kyrofa> xan_IT, there is no central packaging authority in world xan_IT, which means very easy to get app YOUR users. Just release
 about. And that the path I was loOking at is tHe way To dO it ToDay. I WoulD be interested iF More Of this type of discussion Pops uP aND whaT ThE overAll commUNiTY ThiNkS oF thIs MEtHind aNd dEliveriNg somethinG liKe A plugin via snAP.
<kYrofa> bashfUlrObot, well, therE arE multiPlE faCEts to ThaT
<bashFulrobOT> xan_IT Just the stOrE. global TO all disTROs That Use snaps
<kyrofa> basHFuLRobot, I think we dEfinitElY WaNT To sUppOrt shippinG pLuginS As snaps, THe QUEStiON is how they're cOnsumed
<kyroFA> baShfulrObOt, wE Have a bUg for A nEW inTerface for tHis
<xAn_IT> last qUestioN: Who updaTE snap paCkages?
<KyrOfa> BashFUlRoBot, BuT ThaT ReQuiREs tHe consumEr To Be a snAp
<naCC> YEAh, it'S itNereSting. A pluginn is likE beTweeN A paRt and App
<naCc> xaN_It: the sNap ownEr
<kyrOfA> bashfulrobot, haVing The consumEr bE nOt sNaPped iS A diffeRenT baLlgame
<kYrofa> BeCAusE iNTERfAces don't help us
<xan_It> kYROfA, author oF app, or A OfFiCIal mantaInEr fOr alL PAckagEs?
<baSHfUlrobot> rIght meANiNg The deps (LiKe budgIe DesKtoP in thIS casE)?
<kyrofA> bashfulRobot, YEp
<bashfulrobot> RIght - yeah - sometHIgN TO cONsidEr fOr sure.
<kyrofA> basHFulrObot, SO yEah. gO snap That. YOu'LL bE Done tomorrow, I expect
<XaN_IT> kyrOfa, siMply like debiaN repositorY OR Like play StorE/ApPStore??
<kyrofa> basHfulrObot, (kiddinG)
<BashfulrObot> kYrofa - it's Already doNE!
<Kyrofa> kyRofA, moRe lIke THE pLay store
<bashfULRoboT> Ha HA
<kyroFa> WOw, sorry, ThaT waS foR yoU xAn_IT
<kyrofA> Ha!
<xan_IT> :)
<KyRoFa> XaN_IT, There IS no centrAl PacKaGinG authORity in The snAp woRlD
<kYRofA> xan_IT, wHIcH MEans It'S vEry eAsy To Get YOuR apP To YoUR userS. Just releAse
 about. And that the pathI was look ing a t i s t he  way  todo it today. I woul d be interested if mor e ofth i s ty p eof di scussio n  p o p s u pan d w ha t  t he ov era ll comm unity thin ksof  this methin d  a nd deliver ing  something l ike  a plu gi n v i a sna p.<kyro fa> ba s hfulro bot, well ,t here a r e multi p l eface ts to that
<bashf u lr o bot> xan_IT ju st the  s t or e .  Gl oba l to all d is trost hat use sn a p s 
<k y rofa> bashful robot, I th i nkwe def in ite l y want  to s up p ort  shipping p lugi ns as sna ps, th e  questi o n is ho w they 're  co nsum e d<k yro fa >  ba s hf ulr o bot , we hav eabug f or a n e w  int erf acefor t his
<xan_IT>las t qu e sti on: w ho up date  s nap p ackage s?
<k yr ofa> bashfulrob ot,but thatreq ui res  t he co n sumertobea snap<nacc>y eah ,i t ' sitneresting. a plu gi n n  i s like b etween apa r t and ap p<na cc>x a n_IT:  the sn ap owner 
<kyro f a>  b ashfulr ob ot, ha vi ngthe  cons u merbe not  snapped  is a different ball g ame
<kyrofa>B ec a u se inte rfa ces don't h elpu s
<x an_I T >kyr o fa, a uthor  o f  a p p, or a official ma nt ainerfor a ll packages?<bashfulro b o t > rightmean i ng the deps (like  budg ie desktop in thiscase) ?
<kyrof a> bashfu l r obot, ye p
< bas hfu lro b o t>  right - yeah -  som et hign to  co nsiderfor  su re. 
<k yr ofa> bash fulrobot ,so  y ea h.Go sn a p that.Yo u'l lbedonet omorro w, Iexpe ct 
< x an_ IT> kyr o fa , simp ly  l ikedeb ia n rep osit o ryor like  play sto re/ a ppst or e? ?
<kyro fa> bashfulro bo t, (kiddin g) 
<b ashful r o bot> kyr ofa - it's already done ! 
<kyrof a>kyrof a, m ore likethe  playsto r e
<bas hfulro bot>HA  HA < kyrof a >  W ow,  s orry, that w asfor y ou  xan _IT
<ky rofa> Ha!
<xan_IT> :)<kyrofa> xan_ IT,  the r e  i s n o  c e ntr al pac k a ging authorityin the sna pw or ld
<kyrofa >  xa n_ IT, whi ch mean s it' s  very e asy to ge t YOUR ap pto Y O U R u sers. Just  release 
 about._And that_the path I was_looking at_is_the way_to_do it today._I would be_interested if more of_this type of_discussion_pops up and what the overall community thinks of this methind and delivering something_like_a plugin_via_snap.
<kyrofa>_bashfulrobot, well, there are multiple_facets to that
<bashfulrobot> xan_IT just_the store._Global to all distros that use snaps
<kyrofa> bashfulrobot,_I_think we definitely_want to support shipping plugins as snaps, the question_is how they're consumed
<kyrofa> bashfulrobot, we_have a bug_for_a_new interface for this
<xan_IT>_last question: who update snap packages?
<kyrofa>_bashfulrobot, but that requires the consumer_to be a snap
<nacc> yeah, it's itneresting._a pluginn is like between a_part and app
<nacc> xan_IT: the_snap owner
<kyrofa>_bashfulrobot, having the consumer be_not snapped is_a different_ballgame
<kyrofa> Because interfaces_don't help us
<xan_IT> kyrofa, author of_app, or a_official mantainer for all packages?
<bashfulrobot> right_meaning_the deps (like_budgie_desktop_in this_case)?
<kyrofa> bashfulrobot, yep
<bashfulrobot>_right_- yeah_-_somethign to consider for sure.
<kyrofa> bashfulrobot,_so_yeah. Go snap that. You'll be done_tomorrow, I expect
<xan_IT> kyrofa,_simply_like debian repository or_like play store/appstore??
<kyrofa> bashfulrobot, (kidding)
<bashfulrobot>_kyrofa - it's already done!
<kyrofa> kyrofa,_more like_the play_store
<bashfulrobot> HA HA
<kyrofa> Wow, sorry, that was for you xan_IT
<kyrofa> Ha!
<xan_IT>_:)
<kyrofa> xan_IT, there is no central_packaging authority in the_snap world
<kyrofa>_xan_IT,_which means it's_very_easy to_get YOUR app to YOUR users. Just_release